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
{{ message }}
This repository has been archived by the owner on Apr 30, 2024. It is now read-only.
Previewing a page that has parameters in the route is counter intuitive -- the extension injects [name_of_parameter] into the url and opens that page.
Given the information that's available to the extension, I think it will be quite difficult to correctly navigate to a parameterized route.
If it's not possible to find these routes, I think it'd be preferable to simply not offer "right click to preview", or the editor action preview button on any markdown that is in a parameterized route.
If it's not possible to distinguish these routes, I would remove right click to preview, and the preview editor action for all evidence pages.
That is the current v1.0.0 limitation. We did not get the time to dive into templated pages and params rewrite.
Providing preview of those pages might also require better understanding of your data api and how those parameters and dynamic page urls should be created from app routes for Preview.
Fine tuning -- not for the current release.
Previewing a page that has parameters in the route is counter intuitive -- the extension injects [name_of_parameter] into the url and opens that page.
Given the information that's available to the extension, I think it will be quite difficult to correctly navigate to a parameterized route.
If it's not possible to find these routes, I think it'd be preferable to simply not offer "right click to preview", or the editor action preview button on any markdown that is in a parameterized route.
If it's not possible to distinguish these routes, I would remove right click to preview, and the preview editor action for all evidence pages.
See: https://docs.evidence.dev/core-concepts/templated-pages/
The text was updated successfully, but these errors were encountered: