Skip to content
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

[expo-permissions] show correct lib to link if found unrecognized permission #8546

Merged
merged 5 commits into from May 29, 2020

Conversation

jarvisluong
Copy link
Contributor

As mentioned in #8466, this PR address the solution.

Test plan:

  1. Comment out one expo library registerRequesters method
  2. Build Bare-expo and request permission for that library's permission

Expected:

Warning should mention the missing library

Copy link
Member

@tsapeta tsapeta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, good stuff! Thank you so much for many of your contributions 😍

packages/expo-permissions/src/Permissions.ts Outdated Show resolved Hide resolved
packages/expo-permissions/src/Permissions.ts Show resolved Hide resolved
@@ -6,6 +6,8 @@

### 🎉 New features

- If permission is not recognized, show the correct expo package to link. ([#8546])(https://github.com/expo/expo/pull/8046) by [@jarvisluong](https://github.com/jarvisluong)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like you have outdated changelog on your branch 🤔 Those bug fixes below have already been published in 8.2.0

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's right, my master is 35 commits behind the current master, should I rebase now?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I think so, sorry for that 🙂 Unfortunately you may get some issues with rebasing because one of the commit you didn't have is e166a8d which replaced react-native-unimodules as a submodule — we've moved it into the monorepo. Git sometimes has some troubles to resolve such changes right 😞

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be fine now 😅

Jarvis Luong and others added 2 commits May 29, 2020 11:50
Co-authored-by: Tomasz Sapeta <1714764+tsapeta@users.noreply.github.com>
Copy link
Member

@tsapeta tsapeta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool 😄 Last thing, this e2ce040 commit also requires to rebuild typescript files 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants