-
-
Notifications
You must be signed in to change notification settings - Fork 866
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
[FEATURE] Reintroduce keys on Polygon
s
#1657
Comments
This appears to have been removed in 86a080c. Not sure why, will need to investigate. |
There should be methods that don't use keys. For example, I'm not sure how you're building the list of |
Polygon
s
I don't think it makes sense to add a key property to the @sirkalmi if you need custom properties, you can extend from class MyPolygon extends Polygon {
final Key key;
MyPolygon({required this.key, required super.points});
} Voting to close this issue as not planned. |
Thanks for the tip, that's how I solved the problem. |
What do you want implemented?
As a reminder, the 3.1.0 changelog:
[3.1.0] - 2022/12/21
Contains the following additions/removals:
...
Added Keys to Polygons, Polylines, and CircleMarkers - #1402 & #1403
...
What can be used instead if I want to assign an arbitrary object? I want to read it as a result of the onTap event.
What other alternatives are available?
No response
Can you provide any other information?
No response
Severity
Annoying: Currently have to use workarounds
The text was updated successfully, but these errors were encountered: