Changed classes to inherete from compas.Data

[yck011522]

Some of the classes in compas_fab is still based on (object) instead of (Data)

I have selected some of the classes that should support serialization and upgrade them. Upgrading them should be backward compatible. However, it may affect user classes inherited from these classes. This RP does not cover all the classes yet (e.g. classes in backends, reachability map, ghpython and some more). Let me know if you think I should extend to cover all classes.

@gonzalocasas Should I add test files for this?

What type of change is this?

• [ ] Bug fix in a backwards-compatible manner.
• [x] New feature in a backwards-compatible manner.
• [ ] Breaking change: bug fix or new feature that involve incompatible API changes.
• [ ] Other (e.g. doc update, configuration, etc)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [x] I added a line to the CHANGELOG.md file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
• [x] I ran all tests on my computer and it's all green (i.e. invoke test).
• [x] I ran lint on my computer and there are no errors (i.e. invoke lint).
• [x] I added new functions/classes and made them available on a second-level import, e.g. compas_fab.robots.CollisionMesh.
• [x] I have added tests that prove my fix is effective or that my feature works.
• [x] I have added necessary documentation (if appropriate)

[gonzalocasas]

Should I add test files for this?

yes please! they don't need to be super elaborate, but testing the serialization and deserialization on all these classes with some basic data would help ensure they behave properly all the time

[yck011522]

I have revised the list of affected classes:

• CollisionMesh (using existing to_data() from_data() )
• AttachedCollisionMesh (using existing to_data() from_data() )
• Robot (using existing data getter setter)
• RobotSemantics (added new data getter setter and to_data())
• Tool (using existing data getter setter)

The following class is skipped as it maybe redesigned in near future

• PlanningScene

[yck011522]

ping @gonzalocasas

[yck011522]

ping @gonzalocasas

[gonzalocasas]

Cool, thanks for the updates! On my side, I think this is ready to go!