We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/LiUGraphQL/LinGBM/wiki/Introduction-to-the-LinGBM-Project#scenarios describes 2 scenarios: use the the query templates directly, or customize them.
I think it's entirely feasible to keep the main query structure fixed, because the schema is fixed. This includes query params, nesting, field names.
However, GraphQL doesn't have a standardized language for Where clauses. Eg to test Ontotext PLATFORM, in QT10 we need to replace
publicationSearch(field:title, criterion:CONTAINS, pattern:"$keyword") -> publicationSearch(where:{title:{RE:$keyword}})
Does it make sense to templatize only the Where clauses, keeping the rest of the query bodies fixed?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://github.com/LiUGraphQL/LinGBM/wiki/Introduction-to-the-LinGBM-Project#scenarios describes 2 scenarios: use the the query templates directly, or customize them.
I think it's entirely feasible to keep the main query structure fixed, because the schema is fixed. This includes query params, nesting, field names.
However, GraphQL doesn't have a standardized language for Where clauses. Eg to test Ontotext PLATFORM, in QT10 we need to replace
Does it make sense to templatize only the Where clauses, keeping the rest of the query bodies fixed?
The text was updated successfully, but these errors were encountered: