Add ability to pass in customParameters #94
+25
−0
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Custom parameters are not considered, which leads to issues where you're unable to specify provider specific fields mentioned in #57
Issue Number: #57
What is the new behavior?
This takes the variable customParameters and automatically handles appending them to the authenticate call.
Does this PR introduce a breaking change?
This shouldn't break anything as it only operates if the specific customParameters variable is set, and I believe most oauth strategies don't use this.
Looking for guidance if the variable name makes sense for the nest context. I didn't use customParams because I felt like that had a higher likelihood of being used by some strategy.