Support all the ICU collation order options
- Dominant language
- Erlang
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 9
Description
## Summary
Strings in view keys are sorted by the "root" ICU collation order, but other language-specific options are available. Expose this to users as a design document option (like include_design:true or collation:raw)
## Desired Behaviour
Expose this to users as a design document option (like include_design:true or collation:raw)
## Possible Solution
should be as simple as passing the option done once exposed at the couch_ejson_compare level
## Additional context
i18n is good
Contributor guide
Research direction
Start by reading the couch_ejson_compare entry point mentioned in the issue and trace how view-key strings receive the root ICU collation order. Determine how a design document option should expose the requested collation choices, then verify that view-key ordering reflects the selected option. The issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100