-
Notifications
You must be signed in to change notification settings - Fork 184
Workaround Request: Monday API and DSL Dynamic Queries #380
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
Could you please download the schema and attach it here so that I could have a look at it? |
The two relevant sections are:
and
And I've attached MondaySchema.txt as requested. |
The advantage with Python is that you can modify nearly everything. import sys
import graphql
graphql.type.scalars.GRAPHQL_MAX_INT = sys.maxsize |
I am rather new at Python, I'll try to keep that in mind. I wouldn't have thought I could modify a library's parameter like that. I appreciate your help! That's unstuck me. |
In reference to #295 , I've come across the same problem where Monday's API is expecting out-of-spec numerics as Int for a mutation. I'm using the DSL to create dynamic queries and the internal validation is throwing the expected error:
Injecting the necessary identifier as an argument directly fails:
mut = DSLMutation(ds.Mutation.create_item.args( board_id=boardId, group_id=groupId, item_name=item.Name, column_values=... ).select(ds.Item.name))
as does injecting as a variable:
var = DSLVariableDefinitions() mut = DSLMutation(ds.Mutation.create_item.args( board_id=var.boardId, group_id=groupId, item_name=item.Name, column_values=... ).select(ds.Item.name))
and attempting the workaround from 295 (not loading the schema) isn't possible from what I understand, and the schema is required to dynamically make queries. I've already opened a bug on their end, but I'm hoping for a workaround for the dynamic queries in the meantime.
The text was updated successfully, but these errors were encountered: