[geomesa-dev] [JIRA] (GEOMESA-2731) geomesa-jupyter-leaflet assumes avai

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[geomesa-dev] [JIRA] (GEOMESA-2731) geomesa-jupyter-leaflet assumes availability of Leaflet etc

From: "James Srinivasan (JIRA)" <jira@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 23 Oct 2019 20:23:15 +0000 (UTC)
Auto-submitted: auto-generated
Delivered-to: geomesa-dev@xxxxxxxxxxxxxxxx
List-archive: <https://dev.locationtech.org/mhonarc/lists/geomesa-dev>
List-help: <mailto:geomesa-dev-request@locationtech.org?subject=help>
List-subscribe: <https://dev.locationtech.org/mailman/listinfo/geomesa-dev>, <mailto:geomesa-dev-request@locationtech.org?subject=subscribe>
List-unsubscribe: <https://dev.locationtech.org/mailman/options/geomesa-dev>, <mailto:geomesa-dev-request@locationtech.org?subject=unsubscribe>

Title: Message Title

Issue Type:	Improvement
Affects Versions:	2.3.1
Assignee:	James Srinivasan
Created:	23/Oct/19 4:23 PM
Priority:	Major
Reporter:	James Srinivasan

By default, geomesa-jupyter-leaflet assumes Leaflet js, css etc lives in a `js` subdirectory, but the files aren't bundled as such. Proposed solution:

Change API to make `path` parameter and `Option`; if not specified pull from CDN else use specified value.
Update extension of countries.geo.json to .js in order to make browser security mime checks happy

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS

This message was sent by Atlassian Jira

Prev by Date: [geomesa-dev] [JIRA] (GEOMESA-2730) Spatial Partitioning in
Next by Date: [geomesa-dev] [JIRA] (GEOMESA-2732) NiFi - Controller service shared data store is incorrectly disposed
Previous by thread: [geomesa-dev] [JIRA] (GEOMESA-2730) Spatial Partitioning in
Next by thread: [geomesa-dev] [JIRA] (GEOMESA-2732) NiFi - Controller service shared data store is incorrectly disposed
Index(es):
- Date
- Thread

Breadcrumbs