You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using an isolated components, there is the option to pass parameters via the public_options. In matestack-ui-vuejs 3.2.0 beta this variable can still be passed to the isolated components, but is not made visible anymore (inside the component it is empty). Taking a look at the source code, I noticed a new public_context, which is working in the expected way.
Suggestion: remove the public_options completely from isolated components to avoid this "silent failure". In this case, the component would raise an error, letting the user know, that public_options cannot be used anymore
The text was updated successfully, but these errors were encountered:
Sorry for the late response, I will take care of this. We're currently working on releasing 3.2.0 officially. I'm planning on supporting both public_options and public_context in order to not introduce breaking changes.
When using an isolated components, there is the option to pass parameters via the
public_options
. In matestack-ui-vuejs 3.2.0 beta this variable can still be passed to the isolated components, but is not made visible anymore (inside the component it is empty). Taking a look at the source code, I noticed a newpublic_context
, which is working in the expected way.Suggestion: remove the
public_options
completely from isolated components to avoid this "silent failure". In this case, the component would raise an error, letting the user know, thatpublic_options
cannot be used anymoreThe text was updated successfully, but these errors were encountered: