New Salesforce tokens #197
Merged
Conversation
This file contains 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
Come with more restrictive scoping. The comments cannot be posted as FeedItem objects anymore and need to be posted as CaseFeed objects instead. This change retains backward compatibility with the wider scoped tokens while allowing posting with the more restrictive tokens. Signed-off-by: Nicolas Bock <[email protected]>
nicolasbock
force-pushed
the
new-scope
branch
from
88199d7
to
c671d3e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Come with more restrictive scoping. The comments cannot be posted as
FeedItem objects anymore and need to be posted as CaseFeed objects
instead. This change retains backward compatibility with the wider
scoped tokens while allowing posting with the more restrictive tokens.
Signed-off-by: Nicolas Bock [email protected]