We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When embedding a Solara application in a pre-existing Starlette application, automatic routing should consider the root-path command line argument, and generate paths based on the mounted location.
root-path
Automatically generated paths in the Solara app will lead to the root of the Starlette application, where the Solara app is not mounted.
SOLARA_ROOT_PATH="/solara"
SOLARA_BASE_URL="http://localhost:8865/solara/"
http://localhost:8865/solara
http://localhost/page1
http://localhost/solara/page1
An example application utilizing the multi-page demo is available here: https://github.com/nmearl/solara-test
The text was updated successfully, but these errors were encountered:
fix: handle root path in automatic routing (widgetti#908)
1ab6614
maartenbreddels
No branches or pull requests
Expected Behavior
When embedding a Solara application in a pre-existing Starlette application, automatic routing should consider the
root-path
command line argument, and generate paths based on the mounted location.Current Behavior
Automatically generated paths in the Solara app will lead to the root of the Starlette application, where the Solara app is not mounted.
Steps to Reproduce the Problem
SOLARA_ROOT_PATH="/solara"
and/orSOLARA_BASE_URL="http://localhost:8865/solara/"
.http://localhost:8865/solara
).http://localhost/page1
and nothttp://localhost/solara/page1
.An example application utilizing the multi-page demo is available here: https://github.com/nmearl/solara-test
Specifications
The text was updated successfully, but these errors were encountered: