Further fix to configuration classes using ISet, resolving regression with custom 404 pages #19573
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.
Prerequisites
Resolves: #19567
Description
The cause of this issue was another cases of issues involved in the fix #19229, where
ISet
in configuration classes aren't bound.Note that I've added a compatibility suppression for the breaking change, which I don't see how we can otherwise avoid.
Testing
Prepare a custom 404 page as per the instructions in the documentation (though note that I found this didn't work when using the name "404" for the document type and template, and instead used "File Not Found"). With this PR in place, the custom 404 should be displayed as expected.
To check via debugging, put a breaking point at the start of
NotFoundHandlerHelper.GetCurrentNotFoundPageId
and verify theerror404Collection
parameter matches the configured value.Release
Can consider for a 16.0.1, otherwise 16.1.0.