stac-utils / stac-utils/pystac
Determine consistent way to check truthiness and make consistent in the library.
Open
Nobody has claimed this yet.
best practice
- Dominant language
- Python
- Stars
- 463
- Forks
- 134
- Avg merge
- 10h
- Merged PRs (30d)
- 4
Description
E.g. create best practice in the repo and resolve comments such as:
https://github.com/stac-utils/pystac/pull/309#discussion_r624392655
https://github.com/stac-utils/pystac/pull/309#discussion_r624390575
etc
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the discussion comments linked from pull request 309 and then inspect truthiness checks across the library. Define the repository best practice described in the issue, apply it consistently, and resolve the referenced comments; done means the convention is established and the relevant usages follow it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100