-
Notifications
You must be signed in to change notification settings - Fork 3
Add versioning to Structural results #78
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
Add versioning to Structural results #78
Conversation
Making sure there is no BHoM_Guid in the properties, as that will make it impossible to deserialise. The GUID is inserted during the fallback atempt of trying to deserialise as a custom object.
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.
Since I can only judge from the code perspective, I will leave @kThorsager to approve so only putting my review as a comment.
This looks good to me in term of following the procedure for upgrading objects.
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.
Covers all affected objects, doesn't do anything silly and works base on the testfiles.
Small comment on documenting your issues
but LGTM
/azp run Versioning_Toolkit.CheckInstaller |
Azure Pipelines successfully started running 1 pipeline(s). |
NOTE: Depends on
BHoM/BHoM#912
Issues addressed by this PR
Adds in
ModeNumber
as a property to structural results, if not found in the initial dictionary.This is needed for the serialiser to be able to apply the correct creator map when trying to deserialise the results.
Test files
https://burohappold.sharepoint.com/:f:/s/BHoM/Ep9h3lEyopBBvsnP3_HGzSwBncLyPKvZnn0q6AZBwMRwzA?e=j5DdEe
Changelog
Additional comments