-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Rename POST_NOTIFICATION
to POST_NOTIFICATIONS
#35533
Conversation
Base commit: 436da18 |
Base commit: 436da18 |
PR build artifact for fd3cf8a is ready. |
PR build artifact for fd3cf8a is ready. |
@@ -75,7 +75,7 @@ const PERMISSIONS = Object.freeze({ | |||
ANSWER_PHONE_CALLS: 'android.permission.ANSWER_PHONE_CALLS', | |||
READ_PHONE_NUMBERS: 'android.permission.READ_PHONE_NUMBERS', | |||
UWB_RANGING: 'android.permission.UWB_RANGING', | |||
POST_NOTIFICATION: 'android.permission.POST_NOTIFICATIONS', | |||
POST_NOTIFICATIONS: 'android.permission.POST_NOTIFICATIONS', |
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.
Thanks for spotting this. I'm in for a breaking change. The problem is that we shipped this in 0.70 as well, so we'll need to backport this.
Potentially having both is a preferred approach and in 0.72 we can remove the duplicate? (cc @kelset for visiblity)
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.
making sure that I'm following: you want to merge this in main and then cherry pick for both 0.71 and 0.70? I'm ok with that, let's make sure to post comments with links in both release discussions
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.
Asking for your opinion as this is essentially a 'typo' we let pass through. We can add both POST_NOTIFICATION
and POST_NOTIFICATIONS
in the JS API and have the breaking change in .72 OR have this as a breaking change in both .70 and .71
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.
I'd rather not do breaking changes in 0.70 since it's already out. For 0.71 we are still in time to add as a BC. For 0.72 is no problem.
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.
that said, my personal preference would be no breaking changes in 0.70 and 0.71, but yes for 0.72 - but I'm not sure what that would imply here
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.
Ok so let's merge this and pick it on 0.70/0.71
Then let's do the breaking change on main for 72
PR build artifact for 28147f8 is ready. |
PR build artifact for 28147f8 is ready. |
@cortinico Restored to not be a breaking change. |
@philIip has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Summary: After adding `<uses-permission android:name="android.permission.POST_NOTIFICATIONS"/>` on my `AndroidManifest.xml`, I expected to use `PermissionsAndroid.PERMISSIONS.POST_NOTIFICATIONS` but `POST_NOTIFICATIONS` is `undefined` and is named `POST_NOTIFICATION` instead. Every other Android permission is 1:1 in spelling except this one where it lacks `S`. Not sure if this is a welcome change since this can be breaking. Or maybe we can include both with and without `S` to not be a breaking change. Or just keep it as is and close this PR. ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [Android] [Changed] - Rename `POST_NOTIFICATION` to `POST_NOTIFICATIONS` Pull Request resolved: #35533 Test Plan: `PermissionsAndroid.PERMISSIONS.POST_NOTIFICATIONS` should not be `undefined`. Reviewed By: cortinico Differential Revision: D41705866 Pulled By: philIip fbshipit-source-id: a0328b174f0196421565f0cd2b2f1eb509428553 # Conflicts: # packages/rn-tester/js/examples/PermissionsAndroid/PermissionsExample.js
Summary: After adding `<uses-permission android:name="android.permission.POST_NOTIFICATIONS"/>` on my `AndroidManifest.xml`, I expected to use `PermissionsAndroid.PERMISSIONS.POST_NOTIFICATIONS` but `POST_NOTIFICATIONS` is `undefined` and is named `POST_NOTIFICATION` instead. Every other Android permission is 1:1 in spelling except this one where it lacks `S`. Not sure if this is a welcome change since this can be breaking. Or maybe we can include both with and without `S` to not be a breaking change. Or just keep it as is and close this PR. ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [Android] [Changed] - Rename `POST_NOTIFICATION` to `POST_NOTIFICATIONS` Pull Request resolved: #35533 Test Plan: `PermissionsAndroid.PERMISSIONS.POST_NOTIFICATIONS` should not be `undefined`. Reviewed By: cortinico Differential Revision: D41705866 Pulled By: philIip fbshipit-source-id: a0328b174f0196421565f0cd2b2f1eb509428553
Summary: After adding `<uses-permission android:name="android.permission.POST_NOTIFICATIONS"/>` on my `AndroidManifest.xml`, I expected to use `PermissionsAndroid.PERMISSIONS.POST_NOTIFICATIONS` but `POST_NOTIFICATIONS` is `undefined` and is named `POST_NOTIFICATION` instead. Every other Android permission is 1:1 in spelling except this one where it lacks `S`. Not sure if this is a welcome change since this can be breaking. Or maybe we can include both with and without `S` to not be a breaking change. Or just keep it as is and close this PR. ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [Android] [Changed] - Rename `POST_NOTIFICATION` to `POST_NOTIFICATIONS` Pull Request resolved: facebook#35533 Test Plan: `PermissionsAndroid.PERMISSIONS.POST_NOTIFICATIONS` should not be `undefined`. Reviewed By: cortinico Differential Revision: D41705866 Pulled By: philIip fbshipit-source-id: a0328b174f0196421565f0cd2b2f1eb509428553
Summary
After adding
<uses-permission android:name="android.permission.POST_NOTIFICATIONS"/>
on myAndroidManifest.xml
, I expected to usePermissionsAndroid.PERMISSIONS.POST_NOTIFICATIONS
butPOST_NOTIFICATIONS
isundefined
and is namedPOST_NOTIFICATION
instead.Every other Android permission is 1:1 in spelling except this one where it lacks
S
.Not sure if this is a welcome change since this can be breaking. Or maybe we can include both with and without
S
to not be a breaking change. Or just keep it as is and close this PR.Changelog
[Android] [Changed] - Rename
POST_NOTIFICATION
toPOST_NOTIFICATIONS
Test Plan
PermissionsAndroid.PERMISSIONS.POST_NOTIFICATIONS
should not beundefined
.