Simon Leech

A style configuration as shown below will throw thousands of console warnings from the merge.mjs module. This was resolved by wrapping each object in the `cat` in `style`, but this...

Issues found today: 1. Pushed a commit to fix one of them - in styleParser line 164 the call to styleObject was missing the second parameter of the defaultStyle, leading...

I just pushed a commit to update the evalIconObject warning to include the layer key for easier debugging. 

I just pushed a commit to update mvt_clone and vector_layer to have an entry.key so when styleParser throws warnings the layer.key is provided

This doesn't seem to be working currently - ``` json "Boundary Only": { "title": "Boundary Only", "type": "basic", "style": { "fillOpacity": 0.1, "fillColor": "#ffffff", "strokeColor": "#373737", "strokeWidth": 1 } }...

This is also failing with this error , it looks like the style merging isn't working properly  ``` json "style": { "default": { "fillOpacity": 0.5, "fillColor": "#253494", "scale": 0.75...

This doesn't work - ``` json "default": { "style": { "icon": [ { "svg": "filepath" } ] }, "scale": 1, "zoomInScale": 0.15 } ``` Looks like `zoomInScale` doesn't work either....

Also - please can we check that the `graduated_breaks` value is either `greater_than` or `less_than` - and just warn if anything else. Currently you can pass any value to remove...

Just pushed a commit with two minor extra checks in : 1. Add check on cluster.distance

I just pushed a commit to this PR after chatting to @RobAndrewHurst. This PR simply console warns the developer if a value provided in `infoj_order` array does not exist in...