fix for Uncaught InvalidValueError: not an Object #57
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a recent update in the Google Maps API is causing the widget to fail to load with an "Uncaught InvalidValueError: not an Object" if the latitude and longitude fields are blank (e.g. when new objects with GeopositionFields are created without default values)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
a recent update in the Google Maps API is causing the widget to fail to
load with an "Uncaught InvalidValueError: not an Object" if the
latitude and longitude fields are blank (e.g. when new objects with
GeopositionFields are created without default values)