Allow service to update token #29
Merged
Conversation
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
|
@brennon One more update -- please resolve the merge conflicts. |
|
Should be all set. Conflict was in the minified script—only solution was to revert to the minified script and map that do not include other changes in the pull request. |
|
Thanks @brennon ! |
|
My pleasure, @ajbrown. |
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.
I have a need to set the input token with a value received from an API call. Injecting $http into LogglyLoggerProvider's config() isn't possible, and updating the token through the service wasn't possible, either (or, I wasn't able to figure out how to do so.) This commit exposes an inputToken() method on the service that allows the consumer to update the token after configuration.