Check whether measurements exist before removing them#44
Open
Ceremony64 wants to merge 1 commit into
Open
Conversation
This should fix issue ProminentEdge#43
Ceremony64
changed the title
Contributor
|
Hi there, and thanks for submitting this patch! The unfortunate situation is that I no longer have commit permission on this project and can't merge PRs. I also don't know who has, or if they are at all interested in this plugin any more. I think the best would be for someone to fork this project and take over maintenance (I don't use it anymore and haven't done so in several years, so it's not likely I will, unfortunately). I'd be happy to help pointing Leaflet's plugin registry to the new fork in that case. |
|
I'd be happy to fork and help maintain this if Prominent Edge no longer plans to. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This should fix issue #43