Should we have multi-level sorting?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 30
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 6
Description
Nested sorting only makes sense if you expect many duplicate values by your primary axis (e.g., 'number of classes', but not 'relevance' or 'number of runs').
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
No files, tests, or entry points are named. First clarify whether multi-level sorting is wanted and which primary axes should support it; done would require an agreed sorting behavior and a defined scope for the website.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100