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
2.0.3
https://jsfiddle.net/xereda/zbt6sn1h/42/
Change the values for latitude and longitude. No reactivity.
The Geolocation fields update the data object.
The array that deals with geolocation information (MongoDB GeoJSON Object) are not reactive.
Note the following example:
local: { name: 'Empresa XYZ', address: 'Rua Fulano da Veiga, 888', number: 9888, geoLocation: { coordinates: [ 65.234902, 75.349902 ], type: 'Pointer' } }
The only fields that are not reactives are based on the internal array of the Geolocation object. Note this:
The text was updated successfully, but these errors were encountered:
Please check #3988 I think your issue has been fixed in this PR
Sorry, something went wrong.
This is not related to GeoJSON but a duplicate of #3958 & #3979, fixed by #3988 and will be out in 2.0.4.
https://jsfiddle.net/zbt6sn1h/54/
No branches or pull requests
Vue.js version
2.0.3
Reproduction Link
https://jsfiddle.net/xereda/zbt6sn1h/42/
Steps to reproduce
Change the values for latitude and longitude. No reactivity.
What is Expected?
The Geolocation fields update the data object.
What is actually happening?
The array that deals with geolocation information (MongoDB GeoJSON Object) are not reactive.
Note the following example:
local: { name: 'Empresa XYZ', address: 'Rua Fulano da Veiga, 888', number: 9888, geoLocation: { coordinates: [ 65.234902, 75.349902 ], type: 'Pointer' } }
The only fields that are not reactives are based on the internal array of the Geolocation object. Note this:
Nome:Endereço:
Número:
Geolocalização (long):
Geolocalização (lat):
Geolocalização (type):
The text was updated successfully, but these errors were encountered: