[compose] get annotationManager from PointAnnotationGroup #2357
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.
for get featureId to use ViewAnnotation
Summary of changes
It doesn't work when using the combination of PointAnnotationGroup clustering and ViewAnotation.
When creating ViewAnnotationOptions, you can specify the featureId in annotatedLayerFeature to associate it with PointAnnotation. At this time, featureId is obtained from the Annotation as the return value when calling PointAnnotation.create().
However, when using the Copmose Extension, the PointAnnotationManager is hidden, so the annotation ID cannot be obtained.
As a workaround, you can remember PointAnnotationManager and access annotations property of PointAnnotationManager to get the annotation ID when needed.
Currently, annotation IDs are randomly generated, but another method is to specify an ID and create an annotation. However, I think this method requires a large scale of change.
Please consider the contents.
User impact (optional)
Pull request checklist:
@JvmOverloads
,@file:JvmName
, etc).make update-api
to update generated api files, if there's public API changes, otherwise theverify-api-*
CI steps might fail.check changelog
CI step will fail.v10.[version]
release branch fix / enhancement, merge it tomain
firstly and then port tov10.[version]
release branch.Fixes: #2344
PRs must be submitted under the terms of our Contributor License Agreement CLA.