-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Play v3 migration #4402
Play v3 migration #4402
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code looks good and runs locally as expected 🥳
Seen on auth, usage, metadata-editor, leases, collections, kahuna (merged by @andrew-nowak 9 minutes and 1 second ago) Please check your changes! |
Seen on thrall, media-api (merged by @andrew-nowak 9 minutes and 7 seconds ago) Please check your changes! |
Seen on cropper (merged by @andrew-nowak 9 minutes and 19 seconds ago) Please check your changes! |
Seen on image-loader (merged by @andrew-nowak 9 minutes and 24 seconds ago) Please check your changes! |
1 similar comment
Seen on image-loader (merged by @andrew-nowak 9 minutes and 24 seconds ago) Please check your changes! |
What does this change?
Upgrades Grid to Play v3.
The main changes include Grid's move from Akka to Pekko, which involves updating import paths but otherwise behaviour should be the same. To accommodate the move, we also switch from kcl-akka-stream to kcl-pekko-stream, which likewise involves updated import paths but should otherwise behave the same.
How should a reviewer test this change?
Run locally or on the TEST environment, and see if the app continues to perform
How can success be measured?
Who should look at this?
Tested? Documented?