Changed order_source description #362
Merged
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
Changed order_source description from order_RespOnly Added enum object for allowed values
bc-traciporter
approved these changes
Sep 6, 2024
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.
Changed order_source description from order_RespOnly Added enum object for allowed values
DEVDOCS-6009 Re-work of order_source parameter description
What changed?
order_sourceparameter in order_RespOnly YAML object.order_sourcedescription, however there could be more if DEVDOCS-6008 has been merged.Release notes draft
order_sourcedescription to be more specific as to what values can be set for each origin.Anything else?
May need more changes if DEVDOCS-6008 has been merged ahead of it.