-
Notifications
You must be signed in to change notification settings - Fork 5
Layout strategies recipes #47
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
Conversation
| // Configure for client-side layout | ||
| configureViewerOptions(context, { | ||
| needsClientLayout: true, // Enable client layout computation | ||
| needsServerLayout: false, // Disable server layout |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok the root of the problem is this config option, which is almost 8 years old 😅
What shall we do? We could still call it server layout to be consistent with this option, but explain that the layout engine can also run in the frontend?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went with changing client/server to micro/macro.
For the options naming... that's how it is I guess
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we want to rename it, we could mark these two options deprecated and introduce new properties. Don't know if it's worth the effort though.
|
Documenttion about client/server layout strategies