These are now set by the blog app rather than next/prev. Also made
next/prev use them to get their default values. As mentioned on IRC
next/prev could likely be deprecated. Note that there are no tests for
next_page/prev_page as yet (beyond any uses of the defaulting behavior
mentioned above).
While there are no new tests, there are existing tests that check that the blog app generates correct next/prev url links. As these are now generated via the next_page/prev_page there is at least some confirmation that it works.
Coverage increased (+0.02%) to 92.053% when pulling c8994de07f68ae6d17101796a4bc79635f73bf9e on jberger:jberger/feature/next_prev_page into 202370fcf6500047f3566ea6a6bf32432c008ee8 on preaction:master.
These are now set by the blog app rather than next/prev. Also made next/prev use them to get their default values. As mentioned on IRC next/prev could likely be deprecated. Note that there are no tests for next_page/prev_page as yet (beyond any uses of the defaulting behavior mentioned above).
While there are no new tests, there are existing tests that check that the blog app generates correct next/prev url links. As these are now generated via the next_page/prev_page there is at least some confirmation that it works.