HUE-6998 [frontend] Improve configurability of Leaflet maps

Review Request #11757 - Created Oct. 12, 2017 and submitted

Enrico Berti
hue
master
HUE-6998
hue
jgauthier, johan, ranade, romain, weixia, yingc
commit 39b3f42a57769e75711d5e2a51d36541e11fbb39
Author: Enrico Berti <hello@enricoberti.com>
Date:   Thu Oct 12 11:18:06 2017 +0200

    HUE-6998 [frontend] Improve configurability of Leaflet maps

:100644 100644 185797faf3... cdfbe77da8... M	desktop/conf.dist/hue.ini
:100644 100644 f19543ceea... 124ada90d1... M	desktop/conf/pseudo-distributed.ini.tmpl
:100644 100644 3cb8f6dbb4... f72b97b0f0... M	desktop/core/src/desktop/conf.py
:100644 100644 6dc735069a... 1f80029d92... M	desktop/core/src/desktop/static/desktop/js/ko.charts.leaflet.js
:100644 100644 af38ac91d2... cc9729e94e... M	desktop/core/src/desktop/templates/common_header_footer_components.mako
:100644 100644 7c0d54351e... aa428d5dea... M	desktop/core/src/desktop/views.py
Manual on Chrome
  • 0
  • 0
  • 0
  • 1
  • 1
Description From Last Updated
  1. Ship It!
  2. You're assigning a new value to LeafleftGlobals.mapoptions.crs, I'd expect it to stay constant.

    What is the value the second time around? I.e. Does L.CRS contain A -> A mappings as well or will it be undefined

    1. yeah, the thing is.... we cannot specify a JS object in the configuration JSON (so cannot do L.CRS.BLABLA), so in this case the admin will have to do "crs": "BLABLA" on the conf file, and we re-map it to L.CRS.BLABLA :(

  3. 
      
Review request changed

Status: Closed (submitted)

Loading...