-
Couldn't load subscription status.
- Fork 54
Stop returning extra information in GitHub result #100
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
Merged
Parent: Add AzureAD provider
Merged
Changes from all commits
Commits
Show all changes
19 commits Select commit Hold shift + click to select a range
e333053 Stop returning extra information in GitHub result
pbrisbin 1818b79 Remove extra information from BattleNet provider
pbrisbin f4cb337 Remove extra fields in Bitbucket provider
pbrisbin 9381315 Remove extra information from EveOnline provider
pbrisbin ef16a1e Remove extra information from Google plugin
pbrisbin f4391e8 Remove extra fields from Nylas provider
pbrisbin 9916019 Rename qualified import
pbrisbin f492c2d DRY up via setExtra
pbrisbin 3749250 Remove extra fields from Salesforce
pbrisbin 27329aa Remove extra fields from Slack
pbrisbin 615fa24 Remove extras from Spotify
pbrisbin af204bc Remove extra fields from Upcase
pbrisbin 77ab565 Remove unused functions, reduce Prelude interface
pbrisbin cf847ca Add functions for reading credsExtra
pbrisbin 298e5b6 Fixup Google documentation
pbrisbin f52d2e2 Update README
pbrisbin 33590c2 Set the ByteString body at userResponse
pbrisbin b40a405 Make extras accessors safer
pbrisbin 0b2da5f Docs tweaks
pbrisbin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
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.
It may be more convenient for users to use
Either Stringfor all theget*functions. For example, that would let users combine them monadically without writing their own conversions betweenEither StringandMaybe.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 don't know that I follow your reasoning: I think we can't really predict what Monad the user will want to be in, so I don't know that
Eitherwould fit any better at call-sites thanMaybe(they'll almost certainly be inHandler99% of the time)... But I can get behindEitherfor this because it retains information users could choose to silence when inMaybe(e.g.hush), vs the current way where the user would have to invent information when inEither(e.g.note) -- so 👍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.
Well, on second thought I'm not sure. Having these return
Eitherfeels like ifMap.lookupreturned either: that'd be silly because there's only one way it can fail.I think I'm going to keep this for now.