-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
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
Add flag to accept location of config or routes.json #125
Comments
Currently, the CLI looks for the Should we change this behavior @anthonychu ? The current algorithm can be found here: https://github.com/Azure/static-web-apps-cli/blob/main/src/core/utils.ts#L387-L433 |
Yeah. Maybe I need to understand more about how the file discovery logic works. There’s no app_location if proxying to a dev server. I guess one can be inferred if we can find a GitHub action workflow. But I then would like to understand what happens if there are more than one workflow (like in a monorepo). |
Here is how we currently process the start command...
|
When using a dev server (
swa start http://localhost:3000
) or when serving static files from a folder that doesn't contain staticwebapp.config.json (swa start ./dist
), allow the location of the config/routes file to be specified from the CLI.Should be able to specific the path to the file, or the folder containing the file (if both staticwebapp.config.json and routes.json exist, use staticwebapp.config.json).
We should also ensure the current behavior of how the files are found are properly documented.
The text was updated successfully, but these errors were encountered: