-
Notifications
You must be signed in to change notification settings - Fork 20
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
Fix address reactivity in general configuration view #938
Fix address reactivity in general configuration view #938
Conversation
8e82033
to
e869719
Compare
* Change MainVehicleConnetion and WebRTCConnection URIs to use storage and to be reactive * Change video.ts to use new computed property
e869719
to
0c2102f
Compare
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.
0c2102f
to
f7de251
Compare
* Change the way as the URIs are configured to make sure they are reactive and stored properly on storage when using custom ones
f7de251
to
41a9be8
Compare
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.
Lago, there's just one more problem: when the user clicks to activate the custom address in the WebRTC, it reloads the page immediately, even if the custom address that is there is equal to the default one. I think we should check before to see if they are not the same, and not reload in that case.
Closes #406
Fix #924