avoid using deprecated way to create Pekko ParserSettings by pjfanning · Pull Request #13748 · playframework/playframework
Navigation Menu
{{ message }}
playframework / playframework Public
- Notifications You must be signed in to change notification settings
- Fork 4k
Open
pjfanning wants to merge 1 commit intoplayframework:mainfrom
Open
avoid using deprecated way to create Pekko ParserSettings#13748
pjfanning wants to merge 1 commit intoplayframework:mainfrom
avoid using deprecated way to create Pekko ParserSettings#13748
pjfanning wants to merge 1 commit intoplayframework:mainfrom
Conversation
Copy link Copy Markdown
Contributor
pjfanning
commented
Jan 16, 2026
pjfanning
commented
Pull Request Checklist
- Have you read How to write the perfect pull request?
- Have you read through the contributor guidelines?
- Have you referenced any issues you're fixing using commit message keywords?
- Have you added copyright headers to new files?
- Have you checked that both Scala and Java APIs are updated?
- Have you updated the documentation for both Scala and Java sections?
- Have you added tests for any changed functionality?
Helpful things
Fixes
Fixes #xxxx
Purpose
What does this PR do?
Background Context
Why did you take this approach?
References
Are there any relevant issues / PRs / mailing lists discussions?
pjfanning
force-pushed
the
parsersettings
branch
from
d8000a9 to
2f937b7
Compare
Copy link Copy Markdown
Contributor Author
pjfanning
commented
Apr 14, 2026
pjfanning commented
Apr 14, 2026@mkurz would you consider merging this to Play 3.0 or to the dev branch as it improves compatibility with most recent Pekko 1.x releases?
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
Labels
None yet
1 participant