lasp / lasp/latis-python-client
Add ability to control inclusiveness of both sides of selection
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Calling select(..., inclusive=True) will make both the start and end inclusive. It would be good to control both sides independently.
Usually one wants the start to be inclusive and the end to be exclusive, which makes it easier to make multiple requests without overlap (time>=a&time<a+1 to time>=a+1&time<a+2 just works) or to get a whole period of time (time>=2020-01-01&time<2020-01-02 vs. time>=2020-01-01&time<=2020-01-01T23:59:59.9999....).
Contributor guide
No contributing guide indexed for this repository
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
Locate the implementation of select(...) and its current inclusive=True handling, then trace how the selection becomes request parameters. Define separate behavior for the start and end boundaries, and verify that adjacent ranges do not overlap while full-period queries do not require a final timestamp; no test file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100