Repository navigation
service: add service wide configuration - #112
Merged
Merged
Conversation
Contributor
Author
|
@bartonip What do you think about the proposed level of configuration? |
In the case where we need to update several entity sets, we probably don't want to specify HTTP method for each of them. This patch does nothing but enhances user convenience.
Contributor
|
Love this, good job. |
filak-sap
force-pushed
the
service_config_with_http_update
branch
from
June 27, 2020 00:34
69364ab to
5c86e91
Compare
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
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.
In the case where we need to update several entity sets,
we probably don't want to specify HTTP method for each of them.
This patch does nothing but enhances user convenience.