Create a more elegant solution when setting objects to avoid Object.assign

[janechu]

Pull Request

📖 Description

Currently Object.assign must be used when setting objects which have already been defined, this is un-ergonomic as it presupposes knowledge from a developer that a proxy is being used on this object. To circumvent that we now check in the _Changed function whether a proxy is assigned to the object, if not we can assume the user is setting the object and re-proxy the object.

✅ Checklist

General

• I have included a change request file using $ npm run change
• I have added tests for my changes.
• I have tested my changes.
• I have updated the project documentation to reflect my changes.
• I have read the CONTRIBUTING documentation and followed the standards for this project.