-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
feat(platform): allow for configurable API route expose path #319
Conversation
✅ Deploy Preview for analog-app ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for analog-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for analog-blog ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
@brandonroberts currently for e2e testing I modified the |
I'd just keep the |
this adds an option called apiBaseUrl that lets users configure the base path on which the api endpoints are exposed. closes #287
97b38da
to
d3b14d2
Compare
this adds an option called apiBaseUrl that lets users configure the base path on which the api endpoints are exposed.
closes #287
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Which package are you modifying?
What is the current behavior?
API prefix is hard coded.
Issue Number: #287
What is the new behavior?
API prefix can be passed in as an option to the Analog vite plugin
Does this PR introduce a breaking change?
Other information