-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Why is options function deprecated? #6048
Comments
👋 Thanks for opening your first issue here! 👋 If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. |
The thought at the time was that option() shouldn't be publicly available and that individual plugins and components should expose the specific items that can and should be changed via an API. However, it seems like there's a lot of usage of options() and removing it is likely to cause a lot of churn, so, we may end up never removing it. |
This is a question: Why is options function deprecated? I mean, is there a way to set options after a component is constructed? Is there a way to get options later without using "private" property options_?
The text was updated successfully, but these errors were encountered: