Teamable-Analytics / Teamable-Analytics/teamable-backend
Attribute.max_selections needs to account for "as many as you want"
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
We could make null represent this, but that means we need to set max_selections=1 explicitly for categorical single-choice type attributes
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 tracing the Attribute.max_selections handling and the categorical single-choice attribute definitions. Decide how an unlimited selection count should be represented and identify every single-choice case that must explicitly use max_selections=1; done means both behaviors are defined consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100