MongoEngine / MongoEngine/mongoengine
Better error message than 'InvalidQueryError: Cannot resolve field "x"' when x contains '.'
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4h 41m
- Merged PRs (30d)
- 11
Description
Since document fields can't contain '.', and trying to query using objects(**{"a.b":"c"} is a common mistake, MongoEngine should give a more helpful error when failing to resolve a field that appears to contain a '.', informing the user of the Mongoengine form objects(a__b="c").
Actually, if MongoEngine could just auto-convert queries of the first form into the second form it would be best.
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
Start by tracing where InvalidQueryError is raised when a query field contains a dot, then inspect the query-resolution path and existing error tests. The issue's desired outcome is either a clearer message showing the MongoEngine form objects(a__b="c") or automatic conversion from objects(**{"a.b":"c"}); confirm which behavior is acceptable before considering the work done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100