MongoEngine / MongoEngine/mongoengine
Wrong mapfield fields
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4h 41m
- Merged PRs (30d)
- 11
Description
Hi all,
i'm juggling with strange behaviour passing from 0.8.x to 0.15
In 0.8 this code works perfectly:
from mongoengine import *
class Component(EmbeddedDocument):
item = StringField()
class Model(DynamicDocument):
name = StringField()
Components = MapField(EmbeddedDocumentField(Component))
d = { 'name': 'root',
'Components' : {
'first': {'_cls':'Component', 'item':'foo'},
'second': {'_cls':'Component', 'item':'bar'}
}}
m = Model(**d)
for c in m.Components.values():
assert isinstance(c, Component)
But in 0.15 of mongoengine mapfields is populated with dicts, so it fails in the assertion.
This is the main differences:
{'second': <Component: Component object>, 'first': <Component: Component object>}
{'second': {'item': 'bar', '_cls': 'Component'}, 'first': {'item': 'foo', '_cls': 'Component'}}
Is this relathed to DynamicDocument class in any manner?
Thank you
Glauco
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 running the provided Python reproduction against the affected mongoengine version and compare MapField values with the expected EmbeddedDocument instances. Inspect MapField and EmbeddedDocumentField conversion behavior, then add a regression test covering a DynamicDocument map and verify that its values are Component objects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100