Adapter methods: Serialisation to and from ladybug objects

[Tom-Kingstone]

NOTE: Depends on

Issues addressed by this PR

Closes #136

Added the LadybugTools Adapter, with Pull and Push actions, that both use a LadybugConfig action config with a FileSettings property for a json file.

Pull:

This reads the contents of the json file, uses the BHoM serialiser to convert it into a dictionary (or custom object, depending on the layout of the json), checks against the "type" key in the dictionary and tries to convert the deserialised dictionary into a LadybugTools object of that type.

Push:

This takes in a LadybugTools object, and tries to convert it into a json serialised dictionary that can be read and deserialised into a ladybug readable python dictionary.

There were also some changes made to objects in the oM that might need handling in versioning_70.json and the versioning toolkit.

Test files

LBT_Tests.zip
Run this script using the serialised objects here:
Serialised objects.zip

Changelog

Additional comments

[bhombot-ci]

The check code-compliance has already been run previously and recorded as a successful check. This check has not been run again at this time.

[bhombot-ci]

The check documentation-compliance has already been run previously and recorded as a successful check. This check has not been run again at this time.

[bhombot-ci]

The check core has already been run previously and recorded as a successful check. This check has not been run again at this time.

[bhombot-ci]

The check project-compliance has already been run previously and recorded as a successful check. This check has not been run again at this time.

[Tom-Kingstone]

@BHoMBot check compliance
@BHoMBot check required

[bhombot-ci]

@Tom-Kingstone to confirm, the following actions are now queued:

• check code-compliance
• check documentation-compliance
• check project-compliance
• check branch-compliance
• check dataset-compliance
• check copyright-compliance
• check code-compliance
• check documentation-compliance
• check project-compliance
• check core
• check null-handling
• check serialisation
• check versioning
• check installer

[bhombot-ci]

The check code-compliance has already been run previously and recorded as a successful check. This check has not been run again at this time.

[bhombot-ci]

The check documentation-compliance has already been run previously and recorded as a successful check. This check has not been run again at this time.

[bhombot-ci]

The check project-compliance has already been run previously and recorded as a successful check. This check has not been run again at this time.

[FraserGreenroyd]

Good work @Tom-Kingstone nice to get this over the line and deployed for alpha testing with the users

[FraserGreenroyd]

@BHoMBot check versioning
@BHoMBot check compliance
@BHoMBot check required

[bhombot-ci]

@FraserGreenroyd to confirm, the following actions are now queued:

• check versioning
• check code-compliance
• check documentation-compliance
• check project-compliance
• check branch-compliance
• check dataset-compliance
• check copyright-compliance
• check code-compliance
• check documentation-compliance
• check project-compliance
• check core
• check null-handling
• check serialisation
• check versioning
• check installer

[bhombot-ci]

The check code-compliance has already been run previously and recorded as a successful check. This check has not been run again at this time.

[bhombot-ci]

The check documentation-compliance has already been run previously and recorded as a successful check. This check has not been run again at this time.

[bhombot-ci]

The check project-compliance has already been run previously and recorded as a successful check. This check has not been run again at this time.

[bhombot-ci]

The check versioning has already been run previously and recorded as a successful check. This check has not been run again at this time.

[FraserGreenroyd]

@BHoMBot this is a DevOps instruction. I am requesting neutral checks on: unit-tests

[bhombot-ci]

@FraserGreenroyd I have provided neutral checks to the checks requested. These checks will need to be run properly to obtain full results.

[FraserGreenroyd]

@BHoMBot check ready-to-merge

[bhombot-ci]

@FraserGreenroyd to confirm, the following actions are now queued:

• check ready-to-merge