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
Currently setting the component props in playground will evaluate inside the playground's context (browser), lacking access to the server-side environment such as global variables and classes.
The playground README.md seems to imply it should be evaluated in the server-side.
The props don't have to be strings, and they don't even have to be serializable JavaScript objects. Any JavaScript expression that could be evaluated in an SSR enviroment should be supported.
Here's an easy to reproduce example using Date.now():
Set in code
Set in playground
I'm still getting familiar with the project, so maybe some of the above isn't in line with the intended purpose, but in that case it can be clarified in the docs or UI.
The text was updated successfully, but these errors were encountered:
cardoso
changed the title
Props set in playground should be evaluated in the component's context
Display computed prop values in playground
Jun 8, 2024
cardoso
changed the title
Display computed prop values in playground
Props set in playground config should be evaluated in the server for rendering the SSR preview
Jun 8, 2024
cardoso
changed the title
Props set in playground config should be evaluated in the server for rendering the SSR preview
Props set in playground should be evaluated in the server for the SSR preview
Jun 8, 2024
Currently setting the component props in playground will evaluate inside the playground's context (browser), lacking access to the server-side environment such as global variables and classes.
The playground README.md seems to imply it should be evaluated in the server-side.
Here's an easy to reproduce example using Date.now():
Set in code
Set in playground
I'm still getting familiar with the project, so maybe some of the above isn't in line with the intended purpose, but in that case it can be clarified in the docs or UI.
The text was updated successfully, but these errors were encountered: