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
Can I do a PR that changes the source code comment for wrap-server-side-rendering from "...remove this component.." to "..replace this component with wrap-valid-routes.."?
Where:
This extra step you mentioned on slack was not obvious to me, and I assume there will be lots of people who want this URI routing but don't need SSR. I could put an index.html in resource/public as well, although my thinking is not to, just to make it obvious that it is not needed for what is primarily a SSR demo.
The text was updated successfully, but these errors were encountered:
Can I do a PR that changes the source code comment for
wrap-server-side-rendering
from "...remove this component.." to "..replace this component with wrap-valid-routes.."?Where:
This extra step you mentioned on slack was not obvious to me, and I assume there will be lots of people who want this URI routing but don't need SSR. I could put an
index.html
inresource/public
as well, although my thinking is not to, just to make it obvious that it is not needed for what is primarily a SSR demo.The text was updated successfully, but these errors were encountered: