-
Notifications
You must be signed in to change notification settings - Fork 286
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
Breaking change to toggleRotateDistort? #319
Comments
cc @sashadev-sky what do you think? |
@jywarren whatever you think! I had thought because we hadn't revealed that to the outer API as I read that until version 1 of a package is released, you don't strictly have to follow semver convention. but once version 1 is you do. So I have been holding off on major version bump because I am still doing a bit of restructuring esp for #161 |
Sounds good. Let's alert @ChrisLowe-Takor about this just in case it affects that downstream usage. Thanks! |
linking to #105 |
No won't effect me - I'm still using the local hacked up version in the react wrapper. Honestly, that repo has gotten a little stale and I won't have the time to update for at least a few months so don't worry about any breaking changes on my part. |
closing this one now as its resolved! |
I realize the change from
_toggleRotateDistort
to_toggleRotateScale
in https://github.com/publiclab/Leaflet.DistortableImage/pull/229/files#diff-768de6f5429b5761052f2e8e3640ec12R73 could be considered a breaking change -- it definitely needs refactoring in publiclab/mapknitter#782.Should we bump LDI a major version number as a result? Or add an adapter/alias to make it backwards compatible for now until we eventually do make an API-breaking version number update?
The text was updated successfully, but these errors were encountered: