-
Notifications
You must be signed in to change notification settings - Fork 178
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
chore: PoC - handle merging computability in nested attributes #2722
Merged
maastha
merged 12 commits into
CLOUDP-201096-tf-autogen-schema-conv-main
from
CLOUDP-278229-config
Oct 23, 2024
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
c1b30e6
add support for config overrides
maastha 924fe49
Merge branch 'CLOUDP-201096-tf-autogen-schema-conv-main' into CLOUDP-…
maastha 8282070
minor
maastha 35231f5
infer computability for nested
maastha dc25ae0
minor
maastha 9b232a6
minor
maastha e94a4db
Merge branch 'CLOUDP-201096-tf-autogen-schema-conv-main' into CLOUDP-…
maastha 1fd92b3
minor
maastha ce5ec10
minor
maastha af62b39
update test case for nested partial computed attr
maastha 072e3eb
address PR comments
maastha 88f5fbd
lint
maastha 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
There are no files selected for viewing
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
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
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
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
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.
After debugging over the code I was surprised to see the logic for handling nested attributes is within
addOrUpdate
, and not duringmergeAttributes
where you can obtain for each nested attribute what value it has for each operation request/responses. Curious if you thought of this alternative or found limitation for this approach.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.
Not sure I understand completely.
mergeAttributes
is intended as an entry point.can you elaborate what you mean and how that may be better?
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.
I see. So each time an attribute is merged with addOrUpdate all nested attributes are being processed. Leaving some comments on
mergeAttributes
,addOrUpdate
, andmergeNestedAttributes
I believe will be very helpful for future reference.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.
Right. We have to process nested attributes on every merge because create/read responses may contain additional attributes under the same parent attribute name that was initially included from the request.