Skip to content

Add the GeoMan plugin #2124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 22, 2025
Merged

Add the GeoMan plugin #2124

merged 1 commit into from
Apr 22, 2025

Conversation

hansthen
Copy link
Collaborator

@hansthen hansthen commented Apr 7, 2025

The GeoMan plugin is like the Draw plugin, with extra functionality, such as support for Polygons with holes.

@hansthen hansthen requested a review from Conengmo April 7, 2025 14:44
The GeoMan plugin is like the Draw plugin, with extra
functionality, such as support for Polygons with holes.
@hansthen
Copy link
Collaborator Author

@ocefpaf can you have a look?

default_js = [
(
"leaflet_geoman_js",
"https://unpkg.com/@geoman-io/leaflet-geoman-free@latest/dist/leaflet-geoman.js",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use a versioned URL here? I'm also on the fence when doing this for plugins.

BTW, I would recommend all new plugins to be their own package. However, this one does make sense to be here IMO.

Copy link
Collaborator Author

@hansthen hansthen Apr 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My preference is for unversioned most of the time. It causes a lot of small annoyances every time something breaks. It avoids being unable to bring a plugin up to date because too much time has passed and the old versions are no longer supported.

What do you mean "their own package"? You mean like a separate github repository?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep. We took that approach to

  1. Decoupled the plunging development and release from folium
  2. Avoid the extra maintenance burden

@hansthen hansthen merged commit d759140 into python-visualization:main Apr 22, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants