Add support for standalone content pages #622
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
colinrotherham
force-pushed
the
content-page-support
branch
4 times, most recently
from
50ad92e to
4661f5c
Compare
colinrotherham
force-pushed
the
content-page-support
branch
from
7c4dc3a to
e10a17d
Compare
colinrotherham
force-pushed
the
content-page-support
branch
from
e10a17d to
19a2399
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is up for discussion and adds support for standalone content pages
It includes behaviour changes to skip “Content page” types from start page checks
Exit pages
Whilst unlinked pages are currently unreachable (see Privacy Policy below), upcoming exit page fixes in DEFRA/forms-runner#570 additionally prevent access to impossibly-linked content pages
See corresponding PR in forms-runner where I've added a
ContentPageControllerclass: