feat: make all queries/mutations available in the SDK with typed methods (HEXA-1305)#275
Closed
yolanfery wants to merge 5 commits into
Closed
Conversation
yolanfery
commented
Jun 20, 2025
| .pyre/ | ||
|
|
||
| # AI tools settings | ||
| /.claude/settings.local.json No newline at end of file |
Contributor
Author
There was a problem hiding this comment.
let's introduce our new co-worker
yolanfery
commented
Jun 20, 2025
Comment on lines
+179
to
+183
| from openhexa.cli.api import OpenHexaClient, CreateWebappInput, AddToFavoritesInput | ||
|
|
||
| client = OpenHexaClient() | ||
| new_webapp_id = client.create_webapp(input=CreateWebappInput(description="", icon="", name="",workspaceSlug="", url="")).create_webapp.webapp.id | ||
| client.add_to_favorites(input=AddToFavoritesInput(webappId=new_webapp_id)) |
yolanfery
commented
Jun 20, 2025
Comment on lines
1894
to
+1897
| type GenericOutput { | ||
| name: String | ||
| type: String! | ||
| uri: String! | ||
| genericName: String | ||
| genericType: String! | ||
| genericUri: String! |
Contributor
Author
There was a problem hiding this comment.
This small breaking change would be required in the backend as well to make the schema compatible with gqgl
Contributor
Author
|
My recommendation regarding this PR would be to either :
|
I agree, the auto-generated methods are not as practical to contribute such big change to the codebase |
Contributor
Author
|
We all agreed, during our daily yesterday, to put this aside and explore a more manual approach for the queries and mutations. This PR is replaced by #281 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚨 This is an experiment. Let's discuss this before giving it a proper review, thanks.
→ There is already a big limitation : since we need the define a depth limit (in this case 3), each sub-attribute requiring a parameter, is exposing this parameter to the method, resulting in cluttered and irrelevant required parameters. Example :
The key is required for the object, so its required in the resulting python interface :
Leverage https://github.com/timqian/gql-generator to create queries for all queries and mutations defined in the schema
Changes
Screenshots / screencast