Skip to content

Conversation

@gfontorbe
Copy link
Contributor

Documenttion about client/server layout strategies

// Configure for client-side layout
configureViewerOptions(context, {
needsClientLayout: true, // Enable client layout computation
needsServerLayout: false, // Disable server layout
Copy link
Contributor

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?

Copy link
Contributor Author

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

Copy link
Contributor

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.

@gfontorbe gfontorbe merged commit 5821816 into main Dec 1, 2025
3 of 4 checks passed
@gfontorbe gfontorbe deleted the gfontorbe/recipe-layout-strategies branch December 1, 2025 07:58
@github-actions
Copy link

github-actions bot commented Dec 1, 2025

PR Preview Action v1.6.3
Preview removed because the pull request was closed.
2025-12-01 07:59 UTC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants