Skip to content
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

Closed
davidturissini opened this issue Mar 1, 2018 · 11 comments
Closed

Remove dangerousObjectMutation from engine #129

davidturissini opened this issue Mar 1, 2018 · 11 comments

Comments

@davidturissini
Copy link
Contributor

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.

@caridy
Copy link
Contributor

caridy commented Jul 6, 2018

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?

@davidturissini
Copy link
Contributor Author

This was added for observable-membrane and was designed to be an escape hatch for lightning-data-table if I believe. I'm not sure we can remove this yet.

@caridy
Copy link
Contributor

caridy commented Jul 9, 2018

cc @gonzalocordero @jodarove @reiniergs, can any of you confirm?

@jodarove
Copy link
Contributor

jodarove commented Jul 9, 2018

we use it in two places:

1- modules/lightning/datatable/columns
2- modules/lightning/primitive-datatable-tooltip/primitive-datatable-tooltip

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?

@davidturissini
Copy link
Contributor Author

@jodarove You can definitely remove from primitive-datatable-tooltip. I looked at datatable/columns and that component will need to be refactored.

@pmdartus
Copy link
Member

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?

@diervo
Copy link
Contributor

diervo commented Nov 13, 2018 via email

@caridy
Copy link
Contributor

caridy commented Nov 13, 2018

let's remove it.

@diervo
Copy link
Contributor

diervo commented Nov 13, 2018

I'm hearing that @caridy is volunteering to remove occurrences in core! 🎉

@caridy
Copy link
Contributor

caridy commented Nov 13, 2018

there you go diego: #831

now we just need to wait 2 weeks to get this merged 🤣

@pmdartus
Copy link
Member

Fixed by #831

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants