{{ message }}
Repository navigation
[2.9.x] Support Scala 3-style wildcard type arguments in routes files (backport #13972) by @jadenPete - #13973
Merged
Merged
Conversation
(cherry picked from commit efec791)
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
1 participant
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.
Fixes
This PR adds support for Scala 3-style wildcard type arguments in routes files. Currently, Play supports the old
_syntax, but it doesn't support the newer?syntax. This PR fixes that.Purpose
See above.
Background Context
Without support for the new syntax, there's no way to compile generated router code with Scala 3 and use wildcard type arguments.
References
N/A
This is an automatic backport of pull request #13972 done by [Mergify](https://mergify.com).