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
As a developer I would like to be able to pass params to apps built with Vite as path params. This would give me the ability to put resource IDs into my path instead of passing them as query parameters.
Current behavior with the dev server is
Page is defined and served on path test
http://host/test/ returns the app as expected.
http://host/test/id returns the fallback main page
Suggested solution
I've tried digging into the dev server code, but fell short of an actual solution.
What I'd like to see happen is that the path is matched to a best match instead of a perfect match.
so http://host/test/id would match and return the test app even though there's addition path information.
Alternative
I haven't tried this in a prod build, but I imagine the alternate solution would be to prod build and then deliver using a different server.
Description
As a developer I would like to be able to pass params to apps built with Vite as path params. This would give me the ability to put resource IDs into my path instead of passing them as query parameters.
Current behavior with the dev server is
Page is defined and served on path
test
http://host/test/
returns the app as expected.http://host/test/id
returns the fallback main pageSuggested solution
I've tried digging into the dev server code, but fell short of an actual solution.
What I'd like to see happen is that the path is matched to a best match instead of a perfect match.
so
http://host/test/id
would match and return the test app even though there's addition path information.Alternative
I haven't tried this in a prod build, but I imagine the alternate solution would be to prod build and then deliver using a different server.
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: