-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Made it easier to test the frontend against an existing core instance. #23062
Made it easier to test the frontend against an existing core instance. #23062
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!
Thanks! |
This will not work for all REST endpoints that don't have CORS enabled will it? |
Breaking change
Proposed change
I want to be able to test frontend changes on an existing core without having to modify that core's settings.
(not just a development one, production core as well)
I want to avoid the problems I've been experiencing with binding a single folder in two docker containers when using the development flow described for the documentation for the frontend.
Type of change
Added feature to allow building the frontend in such a way that it will connect to a different hassUrl.
Added script to easily start the development build, connect to a core, and host the frontend.
Example configuration
See documentation in script/develop_and_serve
Additional information
I plan to also update the documentation for frontend development to include this option once it has been accepted and included.
Checklist
If user exposed functionality or configuration variables are added/changed: