Replies: 1 comment 3 replies
-
|
In the newest version of the plugins, we changed the way options are set. This is documented in the WarpedMapLayer package underpinning the MapLibre, OpenLayers and Leaflet packages. Options can by set by map, or by layer (for all maps in that layer). This is down done like this (all relevant options listed as example): We would be happy to hear your feedback on this change. Reading your comments, I found that the MapLibre Readme was not as clear about this as I thought, so I noted to improve this. Also, from version 1.0, we should (are going to) work with a CHANGELOG for big changes like this! As always, if you use Allmaps plugins in production, consider locking their version to prevent our changes from breaking your setup. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your thorough reply! I’m glad to hear that the API has just improved and not disappeared. A change log or some kind of announcement feed would be great.
I thought I was doing this; all I had in "@allmaps/maplibre": "1.0.0-beta.38"… which I though would keep me locked on version "overrides": {
"@allmaps/annotation": "1.0.0-beta.35",
"@allmaps/id": "1.0.0-beta.35",
"@allmaps/iiif-parser": "1.0.0-beta.45",
"@allmaps/project": "1.0.0-beta.5",
"@allmaps/render": "1.0.0-beta.76",
"@allmaps/stdlib": "1.0.0-beta.37",
"@allmaps/tailwind": "1.0.0-beta.19",
"@allmaps/transform": "1.0.0-beta.48",
"@allmaps/triangulate": "1.0.0-beta.29",
"@allmaps/types": "1.0.0-beta.20"
}Is there an easier way to do this? |
Beta Was this translation helpful? Give feedback.
-
|
This looks like a question for @bertspaan ! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @rybesh!
Yes, this has been on my to do list for a long time. Until now, our publish/deploy/release process has been quite messy and unstructured. The project deserves better. If you know any good tools for managing releases and changelogs, let me know! About the sub-dependencies: Just having |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have been using
setRemoveColoronWarpedMapLayerwith a June 2025 version of the Allmaps Maplibre plugin without any problems. Today I tried using the most recent version and was surprised to see that this functionality has been removed completely. Is there a replacement? @mclaeysbBeta Was this translation helpful? Give feedback.
All reactions