-
Notifications
You must be signed in to change notification settings - Fork 110
TypeError: 'List' object is not callable #121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
After some trial and error, I narrowed the problem down to the Node created from a Document structure that looks like this: class Bar(EmbeddedDocument):
chee = ListField(StringField(), required=True)
class Foo(Document):
bars = EmbeddedDocumentListField(Bar) I find that if the list field within the embedded document (" I added some models and a test case that reproduces the error to #122. |
Did some digging and the issue appears to be actually with The class Field(MountedType):
[ docstring ]
def __init__(self, type, [...], required=False, [...]):
super(Field, self).__init__(_creation_counter=_creation_counter)
# ... multiple assertions
# type._of_type == String before this, as expected
if required:
type = NonNull(type)
# type._of_type == [String] now Will dig some more because it seems weird nobody else encountered this problem. |
Upon reflection, I figure it's supposed to be this way because of the If that is correct, then I believe method |
I updated #122 with the correction to Renamed the function to |
Closing this because #122 was merged. |
Hello, guys
I updated
graphene-mongo
to0.2.8
in my environment to make use of the new filters (#103), but I cannot for the life of me make it work with the other versions of packages I am using, namelyI've had to pin the packages to certain versions because of this issue with graphene and flask which I am not sure interferes here.
I have tried multiple combinations of versions to these packages, but I either get the "backend" error mentioned in that issue or the following error:
I tried other versions and the problem seems to have appeared in version
0.2.3
ofgraphene-mongo
(I was using version0.2.0
and0.2.1
works as well).Have you guys seen this before? Do you know what could be the cause of it?
Thank you in advance.
The text was updated successfully, but these errors were encountered: