-
Notifications
You must be signed in to change notification settings - Fork 60
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
Add FromIterator impl for FeatureCollection #171
Conversation
Oh right... shoot.
The FromIterator implementation looks great to me.
I don't have anything handy. |
Added some minimal test and minor updates to the docs. The main page doc already quite nicely explains how to convert from geo-types, so I just added an example in the Addresses #170 to some extent |
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.
LGTM!
All my feedback here should be considered optional - feel free to merge when you're ready.
Very happy for this to merge! |
bors r=michaelkirk |
🔒 Permission denied Existing reviewers: click here to make rmanoka a reviewer |
bors r=michaelkirk |
🔒 Permission denied Existing reviewers: click here to make lnicola a reviewer |
Build succeeded: |
CHANGES.md
if knowledge of this change could be valuable to users.Implementation Checklist
To summarize, this is the impl. checklist I'm suggesting:
FromIterator for FeatureCollection
From<&'a T> for Feature where From<&'a T> for Value
, T: BoundingRectand 2 above@michaelkirk @urschrei I realize we can't use
BoundingRect
as we only depend ongeo-types
. Now, I'm a bit hesitant to add impl from geo-types ->Feature
given it's just a conversion toValue
, then toFeature
. The users could do this themselves by converting toValue
then using.into()
method.The PR currently just adds
FromIterator
impl. Should add some tests for this; have an examples collections with bbox to try out with? We could also improve the docs forValue
; currently it is hidden deep, and doesn't explain usage.