Feature - Fix rename apikey to usertoken in ReadMe #49
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
WouterHD
force-pushed
the
feature/FixUsertokenNamingInReadMe
branch
from
d3d761d
to
80661f8
Compare
BerendJonkman
approved these changes
Nov 20, 2019
WouterHD
added
the
waiting-for-final-review
MrJoe
reviewed
Jun 17, 2020
Comment on lines
-19
to
+20
| var client = new SignHostApiClient(new SignHostApiClientSettings("AppName appkey", "apikey or usertoken")); | ||
| var client = new SignHostApiClient(new SignHostApiClientSettings("AppName appkey", "usertoken")); |
There was a problem hiding this comment.
I wouldn't do this as some existing customers only know the term apikey
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.
Usertoken was wrongfully referred to as APIKey in the ReadMe, which caused some confusion.