Bug "type object 'Employee' has no attribute 'sort_argument'"

[royhananwar]

I just clone this repo and try flask example
but when I try to run it without have any changing code
I got an error like this

Traceback (most recent call last): File "./app.py", line 5, in <module> from schema import schema File "/home/examples/flask_sqlalchemy/schema.py", line 28, in <module> class Query(graphene.ObjectType): File "/home/examples/flask_sqlalchemy/schema.py", line 32, in Query Employee, sort=Employee.sort_argument()) AttributeError: type object 'Employee' has no attribute 'sort_argument'

What should I do?

Thank you!

[Cito]

Are you sure you have the version from the cloned repo installed when running the app, not an older version?

[fatore]

I got the same here while following the steps from https://github.com/graphql-python/graphene-sqlalchemy/tree/master/examples/flask_sqlalchemy.

I assumed the proper versions were defined in the requirements.txt file.

[Cito]

That requirements.txt file installs graphene-sqlalchemy from PyPI which is not compatible with the current development version. I think the requirements.txt file should be replaced with this:

-e ../../
Flask-GraphQL

That will install the currently checked out version. Graphene and SQLAlchemy will be automatically installed as dependencies with matching versions. Only Flask-GraphQL needs to be installed explicitly and needs to be added in requirements.txt.

Can you remove the virtualenv directory env and try again with that requirements.txt file?

[jnak]

Good point. There you go #218

[royhananwar]

That requirements.txt file installs graphene-sqlalchemy from PyPI which is not compatible with the current development version. I think the requirements.txt file should be replaced with this:

-e ../../
Flask-GraphQL

That will install the currently checked out version. Graphene and SQLAlchemy will be automatically installed as dependencies with matching versions. Only Flask-GraphQL needs to be installed explicitly and needs to be added in requirements.txt.

Can you remove the virtualenv directory env and try again with that requirements.txt file?

Yes, you are right. I need to use the old requirements.txt
Thank you!
it worked like charms!

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related topics referencing this issue.