Natalie St Jean

Results 10 issues of Natalie St Jean

I noticed that the invert button is causing some weird issues in my browser. The background is being set to black, and then the body is being inverted, which changes...

fto-candidate

These are the errors we're seeing in LBLD when we try to merge the newest changes from LBL: ![FireShot Capture 228 - Job #329 1 - publiclab_leaflet-blurred-location-display - Travis CI_...

bug

This is the same issue we had in https://github.com/publiclab/leaflet-blurred-location/issues/214 ! I've updated the error checking and API key but now both the search by place name and the get placename...

Fixes #242 ( We're happy to help you get this ready -- don't be afraid to ask for help, and **don't be discouraged** if your tests fail at first! If...

In our new browser menu each layer has a "i" icon that you can click on to read more about the layer. However it shows up like this: ![FireShot Capture...

I noticed a bug: This map works great when `simpleMenu: true` but when the browser menu is used the layers are disappearing on zoom. ![Peek 2020-02-11 11-55](https://user-images.githubusercontent.com/49460529/74259256-9fb61500-4cc5-11ea-95a7-f589ce28d12a.gif) Here's the code...

When I tried to include tests for the one-liner implementation I got the error message ``` TypeError: undefined is not a function (evaluating 'L.LayerGroup.EnvironmentalLayers ``` I realized I needed to...

Our current method for displaying a base layer is this: https://github.com/publiclab/leaflet-environmental-layers/blob/7cf1aa1b19e9b3728901465255d13ab3f028a786/example/oneLinerCodeExample.html#L69-L93 I feel like we can clean this up further by saving the baselayer data in the source code instead...

I'm noticing that we are saving custom names like this: https://github.com/publiclab/leaflet-environmental-layers/blob/7cf1aa1b19e9b3728901465255d13ab3f028a786/src/AllLayers.js#L93-L98 This makes the layer display as a more readable "Toxic Release" instead of "toxicReleaseLayer". I feel like we should...

I noticed this the other day and @crisner said she saw the same thing when she updated npm. It is throwing errors for the PLpeopleLayer due to the changes made...