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

Implement missing Feature::set_field_*_list funcs #278

Merged
merged 2 commits into from Jul 3, 2022

Conversation

ttencate
Copy link
Contributor

@ttencate ttencate commented Jun 2, 2022

Also reuse field_idx_from_name instead of duplicating it all over the
place.

  • I agree to follow the project's code of conduct.
  • I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

If you think it's worth a changelog entry, I'll be happy to add one right before merge, to save myself some merge conflicts.

@ttencate ttencate force-pushed the feature/set_list_field_types branch from d420110 to 4743529 Compare June 2, 2022 14:04
Copy link
Contributor

@rmanoka rmanoka left a comment

Choose a reason for hiding this comment

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

lgtm

@rmanoka
Copy link
Contributor

rmanoka commented Jun 23, 2022

@ttencate this PR looks great. Could you add the changelog entry? I'll merge it when done.

Also reuse field_idx_from_name instead of duplicating it all over the
place.
@ttencate ttencate force-pushed the feature/set_list_field_types branch from 4743529 to 0cc4c58 Compare July 2, 2022 08:31
@ttencate
Copy link
Contributor Author

ttencate commented Jul 2, 2022

@rmanoka Done. The clippy fails seem unrelated to this PR.

@rmanoka
Copy link
Contributor

rmanoka commented Jul 3, 2022

Suprising the ci fails as we use bors. This may likely fail but let's see.

bors r+

bors bot added a commit that referenced this pull request Jul 3, 2022
278: Implement missing Feature::set_field_*_list funcs r=rmanoka a=ttencate

Also reuse field_idx_from_name instead of duplicating it all over the
place.

- [x] I agree to follow the project's [code of conduct](https://github.com/georust/gdal/blob/master/CODE_OF_CONDUCT.md).
- [x] I added an entry to `CHANGES.md` if knowledge of this change could be valuable to users.
---

If you think it's worth a changelog entry, I'll be happy to add one right before merge, to save myself some merge conflicts.

Co-authored-by: Thomas ten Cate <ttencate@gmail.com>
@bors
Copy link
Contributor

bors bot commented Jul 3, 2022

Build failed:

@rmanoka
Copy link
Contributor

rmanoka commented Jul 3, 2022

bors r+

@bors
Copy link
Contributor

bors bot commented Jul 3, 2022

Build succeeded:

@bors bors bot merged commit f1ca1c9 into georust:master Jul 3, 2022
@ttencate
Copy link
Contributor Author

ttencate commented Oct 11, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants