hyperstack-org / hyperstack-org/hyperstack

Option to not put HyperstackOpts and ReactiveRecordPublicColumnsHash into HTML

Open
#270 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
538
Forks
41
PR merge metrics
No merged PRs in 30d

Description

I have a layout where I am rendering several different components, and each of them return the HyperstackOpts and the ReactiveRecordPublicColumns hash. For a large application, this adds a significant amount to the page that isn't even used, and can slow things down.

A case where this can actually be a problem, is with fragment caching. If caching a prerendered component, it would cache the csrf token in HyperstackOpts and cause that to be invalid and break the client.

I've managed to workaround this by `gsub`ing out that stuff, and manually rendering those in the layout outside of a cached component. But it would be nice to be able to specify not to return it with a prerendered component, and possibly have a helper method to render it somewhere else in the layout.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.