Uh oh!
There was an error while loading. Please reload this page.
bugfix: properly serialize nested attrs classes - #38591
Merged
Merged
Conversation
uranusjr
approved these changes
Mar 29, 2024
jscheffl
approved these changes
Mar 29, 2024
tomrutter
commented
Mar 29, 2024
ContributorAuthor
Thanks for review and merge! |
ephraimbuddy pushed a commit
that referenced
this pull request
Mar 31, 2024
Co-authored-by: Tom Rutter <tom.rutter@zurich.com> (cherry picked from commit 7613795)
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
closes: #38540
Running attr.asdict with recurse=False allows the serialize function to later serialize the nested attr objects consistently. With recurse=True, they remain as dict and don't deserialize back to the original class.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.