v2.1.0 release #103
Merged
v2.1.0 release #103
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
Co-authored-by: CDR Open Source <[email protected]>
Co-authored-by: Farooq Kotwal <[email protected]>
Co-authored-by: CDR Open Source <[email protected]> Co-authored-by: Farooq Kotwal <[email protected]>
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| } | ||
| } | ||
| } | ||
| else if (request.Form.ContainsKey("scope")) |
Check warning
Code scanning / SonarCloud
Use model binding instead of reading raw request data
|
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.
Checklist: (Put an
xin all the boxes that apply)mainbranch has been set as thebasebranch to merge changes of the pull request.CHANGELOG.mdfile as appropriate.What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
v2.1.0 release
What is the current behavior? (You can also link to an open issue here)
What is the new behavior? (if this is a feature change)
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:
v2.1.0 release