facet_m2m gets confused by multiple relationships
Open
Nobody has claimed this yet.
bug
faceting
medium
- Dominant language
- Python
- Stars
- 11.5k
- Forks
- 904
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 18
Description
I got this for a database I was playing with:
I think this is because of these three tables:
Contributor guide
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
Reproduce the reported facet_m2m behavior with a database containing the three relationships shown in the issue's screenshots. Start by tracing how facet_m2m handles multiple relationships, then verify that the resulting facets are correct for this schema and add coverage for the reproduced case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100