Closed davidfurey closed 6 months ago
mobile-n10n:eventconsumer
to CODEmobile-n10n:schedule
to CODEmobile-n10n:football
to CODEmobile-n10n:reportextractor
to CODEmobile-n10n:fakebreakingnewslambda
to CODEmobile-n10n:report
to CODEmobile-n10n:notification
to CODEmobile-n10n:slomonitor
to CODEmobile-n10n:registration
to CODEmobile-n10n:notificationworkerlambda
to CODETests on Common and API-models haven't been run, and should be before this is merged
I have tested the latest snapshot and a test notification has been sent successfully.
It appears that we have to exclude
com.typesafe.play
bundles explicitly when the project depends on"ai.x" %% "play-json-extensions"
(because it brings in the old play-json transitively). I am wondering whether we should also add the exclusion rule to the subprojectnotification
,registration
andreport
? Or have I missed anything (as the notification and registration API can work properly on CODE)?
You are correct, the exclusion should also be applied to notification, registration and report. I've pushed a commit with that
@waisingyiu do you think we have done sufficient testing to merge this?
@waisingyiu do you think we have done sufficient testing to merge this?
Yes, I think the testing should be sufficient. I ran the following tests
I am happy to merge it and keep an eye on it tomorrow morning if it helps?
I am happy to merge it and keep an eye on it tomorrow morning if it helps?
That would be great, thanks!
What does this change?
Minimal changes to upgrade to Play 3.0
How to test
How can we measure success?
Have we considered potential risks?
Images
Accessibility