-
Notifications
You must be signed in to change notification settings - Fork 40
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
Disable state serialization for a request #148
Comments
It is currently not possible to disable state serialization for a request/context, but it wouldn't be huge change to support that feature. With that said, we will be releasing a new minor version of Marko Widgets with a much-improved state/widget config serialization mechanism that supports circular dependencies and it will automatically de-dupe repeated objects. We hope to have the new version available in a week or two. Would you still want to disable state serialization if we optimized how state was serialized to the browser? |
Great! I believe will not be necessary to disable state serialization once we have this improved serialization feature released. But, for now, would be very helpful to have it disabled. What would be the necessary changes to disable it? |
Any thoughts on the API for disabling state serialization? It would need to be set before rendering any components. Maybe introduce a tag that could be placed at the top of the page and that produces no output?: <widgets-configure serialize-state=false/> FYI, here is the related code:
/cc @mlrawlings @philidem |
I like the idea, so I created the |
Using |
Is it possible to disable the
data-w-state
serialization for a request?The text was updated successfully, but these errors were encountered: