Daniel
Daniel
As this feature matures we could perhaps ship it as a default with a new major version of Parse Server. I think it is a welcome improvement of usability to...
> This seems like a convenient feature I think convenience and ease of use are important - especially for newer developers. There is a learning curve with Parse and this...
Well any initial release of software is expected to become more stable over time. All I’m saying is that there may be errors thrown specifically relating to the dot notation...
Ahh, ok. Sorry we got a bit carried away. I'll continue to test this feature on my servers / sdks and let you know when I feel it's ready.
> if you enabled the feature in a branch and did a regex replace for all tests from .get(...) to dot notation, it may give you an indication whether there...
> Here is an example that would break If you were using that code _without_ dot notation, `obj.get('x')` would be undefined, but with the feature, it will be saved. So...
> To merge this, we'd need to be sure enabling it doesn't break anything inside Parse Server. I actually manually deployed the complied lib folder to my Parse Server, and...
> So you only apply the new logic if the requested property is actually an existing attribute. I tried this, but as getting attributes calls `.attributes`, and then `.className`, `.id`...
Also noting that if we get `if (Object.keys(this.attributes).includes(key))` to work, setting a value to a new key will never work, e.g: ``` const obj = new Parse.Object('Proxy'); obj.name = 'name'...
I have primarily used this code for frontend use via subclassing Parse Object. Have used minimally with cloud code. Only issue I have found is that setting nested objects don’t...