GDB-10226: change import settings model #1390
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
## What Moved the "contextLink" property from the top level to the "parserSettings" object within the import settings model. ## Why During the update of import functionality, it was decided to relocate the "contextLink" property from its previous location under "parserSettings" to the root level of the import settings model. This change was necessary to align with the updated requirements for import settings, but this would break any existing integrations with this API and is not ok for a minor release. ## How The "contextLink" was moved to previous place in the "parserSettings".
|
yordanalexandrov
approved these changes
May 10, 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.
What
Moved the "contextLink" property from the top level to the "parserSettings" object within the import settings model.
Why
During the update of import functionality, it was decided to relocate the "contextLink" property from its previous location under "parserSettings" to the root level of the import settings model. This change was necessary to align with the updated requirements for import settings, but this would break any existing integrations with this API and is not ok for a minor release.
How
The "contextLink" was moved to previous place in the "parserSettings".