JuliaData / JuliaData/DataAPI.jl
Add `Selector` abstract type for ecosytem compat, and rethink `Between`
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 35
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
DimensionalData.jl defines a Selector abstract type and selectors Between, Near, At, Where, and Contains.
AxisKeys.jl also defines Selector and Near and Inervals selectors (ping @mcabbott)
It would be useful to standardise these so we can all use the simplest words without clashes, and this is probably the place for that.
We could define Selector here, and make Between <: Selector. Near could also move here to avoid the (maybe less common) clashes between AxisKeys.jl and DimensionalData.jl, if @mcabbott is also interested in sharing these types.
Between in DD holds a 2-tuple of any types, while here it has two fields limited to Union{Int,Symbol}.
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
Start by comparing the selector definitions described in DimensionalData.jl and AxisKeys.jl, including Selector, Between, Near, and the interval selectors. Resolve which shared types and compatibility rules should be adopted; done means the project has an agreed standardized selector API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- api, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100