Repository navigation
http: replace nullable Boosted with HtmxRequestKind - #70
Merged
Merged
Conversation
When Boosted changed from bool to bool?, we missed that nullable types cannot be used as attribute arguments. Setting Boosted in [HtmxRequest] then failed with CS0655. Replace it with Kind and HtmxRequestKind. The enum preserves all three options and makes the intent clearer: Any, Boosted, or NonBoosted.
This file contains hidden or 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
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.
Changing
Boostedfrombooltobool?introduced an overlooked limitation:nullable types cannot be used as attribute arguments, causing
CS0655.Replace
BoostedwithKindandHtmxRequestKind. The enum keeps all three options -Any,Boosted, andNonBoosted, and makes the intent clearer.