-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
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
Remove dangerousObjectMutation from engine #129
Comments
Do we need to wait until we remove the traverse membrane to be able to remove this? or should we be able to remove this now? |
This was added for |
cc @gonzalocordero @jodarove @reiniergs, can any of you confirm? |
we use it in two places: 1- modules/lightning/datatable/columns I can get why we use it in (1) (and as we speak we plan to remove it). but i don't know why we should use it in (2) @davidturissini do you have any idea why the second usage? |
@jodarove You can definitely remove from |
I don't see any code that is referencing this API anymore in the global components. Is there any other blocker with removing this API? |
O yes it is used.... but I agree we should kill it before GA
…On Tue, Nov 13, 2018 at 4:54 AM Pierre-Marie Dartus < ***@***.***> wrote:
I don't see any code that is referencing this API anymore in the global
components. Is there any other blocker with removing this API?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#129 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABH0qOqSzLtaGaqptE4xqVcHkxTsoRo-ks5uusEQgaJpZM4SYzye>
.
|
let's remove it. |
I'm hearing that @caridy is volunteering to remove occurrences in core! 🎉 |
there you go diego: #831 now we just need to wait 2 weeks to get this merged 🤣 |
Fixed by #831 |
Description
We recently added
dangerousObjectMutation
method on the engine for component authors to opt-out of read-only membrane in public props. This method is designed to be a temporary stop-gap, and should be removed ASAP.The text was updated successfully, but these errors were encountered: