We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Iterate on locker-membrane for reactivity.
locker-membrane
Reactive State
New membrane APIs (hooks for touching/updating/mutating)
subscribeToMutations notifyMutation
API:
const membrane = new ReactiveMembrane(() => {}); const foo = { bar: 'baz', } membrane.getReadOnly(foo); // get read only reactive membrane membrane.getReactiveProxy(foo); // get read/write reactive membrane
The text was updated successfully, but these errors were encountered:
What you think about using a consistent naming for the 2 APIs? For example membrane.getProxy and membrane.getReadOnlyProxy
membrane.getProxy
membrane.getReadOnlyProxy
Sorry, something went wrong.
davidturissini
No branches or pull requests
Description
Iterate on
locker-membrane
for reactivity.Reactive State
objects (tuple of full reactive proxy, and read only)New membrane APIs (hooks for touching/updating/mutating)
subscribeToMutations
notifyMutation
API:
The text was updated successfully, but these errors were encountered: