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 layer id annotations #2505

Merged
merged 1 commit into from
Jun 14, 2024
Merged

Rename layer id annotations #2505

merged 1 commit into from
Jun 14, 2024

Conversation

louwers
Copy link
Collaborator

@louwers louwers commented Jun 13, 2024

I think @TimSylvester missed this one in #2452

This PR also renames save instance state keys while we're at it.

Closes #2498 thanks for the report @Fabi755, appreciate it.

@louwers louwers requested a review from TimSylvester June 13, 2024 22:28
@louwers louwers self-assigned this Jun 13, 2024
@louwers louwers requested a review from HarelM June 14, 2024 10:45
Copy link
Collaborator

@HarelM HarelM left a comment

Choose a reason for hiding this comment

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

Is this a breaking change?

@louwers
Copy link
Collaborator Author

louwers commented Jun 14, 2024

@HarelM No it's just an opaque id meant not to conflict. But we only changed it in the C++ not in Java, so that would introduce a bug.

As long as people use the constants for the saved instance state keys and not manually copy the values, should also be no problem to change them.

@louwers louwers merged commit 46f2fa1 into maplibre:main Jun 14, 2024
22 of 24 checks passed
@louwers louwers deleted the maplibre-rename branch June 14, 2024 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging this pull request may close these issues.

Missing com.mapbox replacement on annotation layer ID
2 participants