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.id() can be String and Number #1033
Conversation
This pull request has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
This pull request has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
This pull request has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
*/ | ||
@Nullable | ||
public String id() { | ||
public Object id() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would be great to include as idAsString and idAsNumber facility methods (if the type doesn't match throw an exception).
Stale. |
According to GeoJson spec Feature.id can be String or Number.
This will be Semver-Major change as
id()
has to returnObject
to support both String and Number.After #1025 lands, CarmenFeature.id() should be modified as well.
closes #914