-
Notifications
You must be signed in to change notification settings - Fork 4
[LIB-783] - Correct endpoints check methods #213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
478e325
[LIB-783] - move logic checking available endpoint request methods to…
ilu2112 d84dbab
[LIB-783] - move logic checking available endpoint request methods t…
ilu2112 0303de2
[LIB-783] - check available http methods for endpoint calls: apply ch…
ilu2112 88d118c
[LIB-783] - tests
ilu2112 35de4a6
[LIB-783] - fix user integration tests
ilu2112 b7606bc
[LIB-783] - Pass method type to resolve_endpoint as named parameter.
ilu2112 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
[LIB-783] - move logic checking available endpoint request methods to…
… Meta class, apply changes to ScriptEndpoint model
- Loading branch information
commit 478e325f172f4673b55cd9f23062a755c9df4ace
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -142,6 +142,10 @@ def resolve_endpoint(self, name, properties): | |
|
|
||
| return endpoint['path'].format(**properties) | ||
|
|
||
| def is_http_method_available_for_endpoint(self, http_method_name, endpoint_name): | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
| available_methods = self.get_endpoint_methods(endpoint_name) | ||
| return http_method_name.lower() in available_methods | ||
|
|
||
| def get_endpoint_query_params(self, name, params): | ||
| properties = self.get_endpoint_properties(name) | ||
| return {k: v for k, v in six.iteritems(params) if k not in properties} | ||
|
|
||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In:
is
get_endpointwhich is:Maybe we should add check in
resolve_endpointfor that? Would be much cleaner. What do you think?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@opalczynski Fine :)