Skip to content
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

Save info when dumped and loaded by Marshal #72

Merged
merged 3 commits into from
Oct 2, 2024

Conversation

wildmaples
Copy link
Contributor

@wildmaples wildmaples commented Nov 24, 2022

Previously, ROS did not play well when being dump and loaded with Marshal because the options from ROS did not translate through the serialization. This change saves the information through marshal_dump and then reassigns the information to ROS instance when the object is loaded.

(ideally) Fix: #71

Previously, ROS did not play well when being dump and loaded with Marshal because the options from ROS did not translate through the serialization. This change saves the information through marshal_dump and then reassigns the information to ROS instance when the object is loaded.
@wildmaples wildmaples force-pushed the fix-marshal-load-issue branch from c569909 to 2d2271d Compare November 24, 2022 02:51
@wildmaples wildmaples changed the title Dump and load options and sub_elements Save info when dumped and loaded by Marshal Nov 24, 2022
@wildmaples
Copy link
Contributor Author

Closing due to repo's inactivity

@wildmaples wildmaples closed this Apr 26, 2024
@Jack12816
Copy link

@wildmaples Could you open this again? Looks like @aetherknight had time this year to perform some interactions, and this is still an issue on a 50 mio downloads gem. :(

@wildmaples wildmaples reopened this Oct 1, 2024
@aetherknight
Copy link
Owner

I’ll look into reviewing and merging this tonight

@aetherknight aetherknight merged commit 7ece1dd into aetherknight:main Oct 2, 2024
6 checks passed
@aetherknight
Copy link
Owner

Released as part of 1.3.0

@Jack12816
Copy link

Thank you very much! ❤️

@aetherknight
Copy link
Owner

@Jack12816 @wildmaples FYI, since this is an API-breaking change, I have released 1.3.1 that reverts this change, but it's re-added in a version 2.0.0, in order to preserve semver. (See #79 for more discussion)

@Jack12816
Copy link

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to deserialize recursively
3 participants