Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Resolve email scope support
See original GitHub issueWe’re aware that we indicate support for an email scope in the documentation, but this support doesn’t actually work in the platform by providing developers with user email values.
This epic entails deciding what to do about email scope support. We can either choose to fulfill the functionality described by the documentation currently, expand that functionality during a proper implementation, or remove it entirely.
If we do decide to implement its functionality, we may want to make email provision optional for users so they can authenticate to apps and provide other permissions but not their email value necessarily.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This should be addressed by the 2 PRs referenced above ^
That sounds fine. I see this as connected to the Radiks notification work, and can’t really consider that box checked until this is done. Would like this prioritized and included in the next browser release please. cc @hstove