-
Notifications
You must be signed in to change notification settings - Fork 185
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
Document the "dsl" module/language #82
Comments
Btw, there is also an "improved-dsl" feature branch that has not yet been merged if anybody wants to look into this. |
FYI I added a very small example of the dsl module in the readme in PR #114 |
Note: I have completely refactored the DSL code in PR #169
I've looked into the improved-dsl branch and it sounds quite obsolete except maybe for the |
I am up for that change as well, maybe on same branch as refactored DSL 🤔 |
Refactoring of the DSL code. The DSLSchema only needs a schema, a Client is no more needed. New dsl_gql function to convert the DSL operations into a Document This allows DSL queries to be executed in a session instead of a client (Solves #138) Added typing annotations Added code documentation and sphinx docs (Solves #82) Supports Subscriptions Fix nested input arguments Allow to set the alias directly in the select method Allow multiple operations in a document Allow to set the operation name
Fixed in v3.0.0a5 |
The somewhat obscure "dsl" module/language included in gql should be documented. It is currently unclear to me where it is coming from, whether it mimics an existing thing or was an invention of @syrusakbary. Does anybody know?
Note: I'm not talking about the "schema definition language" of GraphQL here, but about the dsl module in gql. I think the name "dsl" is also a bit misleading because it usually means "domain specific language", but this is actually a general purpose language and not domain specific in the usual sense of "application domain specific". As far as I understand it is just an alternative way to express GraphQL documents in Python instead of JSON, Similar to the "SQL Expression language" in SQLAlchemy which allows writing SQL queries in Python.
The text was updated successfully, but these errors were encountered: