171 - Fix path parameter format #172
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
Codecov Report
@@ Coverage Diff @@
## main #172 +/- ##
==========================================
+ Coverage 91.83% 91.88% +0.04%
==========================================
Files 8 8
Lines 821 826 +5
==========================================
+ Hits 754 759 +5
Misses 67 67
Continue to review full report at Codecov.
|
Andy-Grigg
approved these changes
Mar 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #171
Accompanying code generator generates path parameters with placeholder values like
http://api.com/resource/{param}, this was being incorrectly handled, resulting in invalid resources.This PR is some minor refactoring to improve testability, adding some tests for path and query parameter construction, and the fix for the underlying issue.