Fixed issue with non-default lat/long fields, and not providing defau…

…lts when field names were not specified
mikebronner · Jun 26, 2019 · d4d5eb6 · d4d5eb6
1 parent 0d711fb
commit d4d5eb6
Show file tree

Hide file tree

Showing 3 changed files with 11 additions and 3 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -3,8 +3,16 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
 and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
+
 ## [Unreleased]
 
+## [0.1.3] - 2019-06-26
+### Fixed
+- an issue where the detail screen didn't read non-default `latitude` and
+  `longitude` fields.
+- an issue on the detail screen where it didn't apply the default field names
+  when not provided.
+
 ## [0.1.2] - 2019-06-24
 ### Fixed
 - scroll and touch zoom behavior, where the marker would move off center when

diff --git a/dist/js/field.js b/dist/js/field.js
diff --git a/resources/js/components/DetailField.vue b/resources/js/components/DetailField.vue
@@ -88,8 +88,8 @@ export default {
 
         setInitialValue: function () {
             this.value = {
-                latitude: this.field.value.latitude || 0,
-                longitude: this.field.value.longitude || 0,
+                latitude: this.field.value[this.field.latitude || "latitude"] || 0,
+                longitude: this.field.value[this.field.longitude || "longitude"] || 0,
             };
         },
     },