RFC: Pt. 3 - Evaluate use of native Proxy

[snewcomer]

This is just an evaluation step. Not necessarily saying we should go with it. Need to evaluate after removing Relay implementation.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy

Downside is no IE support

Ref #317 #323 #322

[poteto]

I investigated this in https://github.com/poteto/validated-proxy, but gave up on it as there wasn't an obvious way to handle async sets and return a promise. I may have missed something though.

[snewcomer]

@poteto Great point. Do you feel like returning a promise from a setter is necessary? Right now, set returns a ValidationResult. It seems like it was deemed true.

Setter happens sync. Validation may be async. However, I'm wondering about the case for returning a ValidationResult from set. We could require the user to call .validate() to get a Promise<ValidationResult> back.

I believe this would allow us to use Proxy and probably squash some persistent issues around our current implementation.

Would love to hear other's thoughts as well!