-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Rename css classes #4
Comments
I wasn't aware this project had css in it... |
BTW, any help with the other two issues I just opened would be greatly appreciated! |
The suggestion of keeping both classes might have prevented it from being a breaking change, and a minor semver bump would have made sense. As it stands, this introduced a breaking change without the requisite semver major bump, so it might cause issues for consumers of this package. I know it did for us! |
Same here, actually it triggered this update. Since that breaking change was pushed to maplibre-gl-js, do we have much choice here? |
No, I think it's a backwards compatibility issue with maplibre not using semver correctly. We are doing a similar change in our internal libraries as you do in yours. |
I basically pushed this to maplibre-gl. |
Maplibre 1.15.0 introduces a breaking change: css class names renamed from
mapboxgl-*
tomaplibregl-*
(see https://github.com/maplibre/maplibre-gl-js/blob/main/CHANGELOG.md, maplibre/maplibre-gl-js#83)ngx-maplibre-gl 's css classes names should match this change.
The text was updated successfully, but these errors were encountered: