Skip to content
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

Closed
aprilmay opened this issue Jul 4, 2021 · 6 comments
Closed

Rename css classes #4

aprilmay opened this issue Jul 4, 2021 · 6 comments

Comments

@aprilmay
Copy link

aprilmay commented Jul 4, 2021

Maplibre 1.15.0 introduces a breaking change: css class names renamed from mapboxgl-* to maplibregl-* (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.

@HarelM
Copy link
Collaborator

HarelM commented Jul 4, 2021

I wasn't aware this project had css in it...
Care to submit a PR to resolve this?

@aprilmay aprilmay mentioned this issue Jul 4, 2021
@HarelM HarelM closed this as completed in f327846 Jul 4, 2021
@HarelM
Copy link
Collaborator

HarelM commented Jul 4, 2021

BTW, any help with the other two issues I just opened would be greatly appreciated!

@bendman
Copy link

bendman commented Jul 6, 2021

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!

@aprilmay
Copy link
Author

aprilmay commented Jul 6, 2021

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?

@bendman
Copy link

bendman commented Jul 6, 2021

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.

@HarelM
Copy link
Collaborator

HarelM commented Jul 6, 2021

I basically pushed this to maplibre-gl.
I actually asked if the change in css should be major or minor and other have agreed it was minor and not major.
The extra size in the package is critical so duplicating the styles was not a recommended step.
Also, since not many people are using maplibre yet we agreed that pushing this forward early on would be the right step.
In any case, feel free to join the slack and github issues communication and share your opinion.
Bare in mind that some opinions will be accepted and other won't, this is the open source way :-)

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

No branches or pull requests

3 participants