-
Notifications
You must be signed in to change notification settings - Fork 203
fix(sdk-codegen): make run_inline_query response type generic #1730
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
Open
marc-wilson
wants to merge
2
commits into
looker-open-source:main
Choose a base branch
from
marc-wilson:fix/run-inline-query-json-type
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, if
streameris true, the generic type parameter is omitted (genericsis set to'') and the callback return type is hardcoded toPromise<${mapped.name}>(which resolves toPromise<string>).To ensure that streaming versions of format-dependent methods also benefit from the generic response type, we should use
this.responseTypeName(method)in the callback signature and allowgenericsto be generated for streaming methods as well.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, and agreed in principle — but I'd like to keep this specific to the non-streaming path for now.
The streaming variant's callback receives the raw
Response/Readable(e.g. for piping a download to a file), so its return type is really "whatever the caller's callback resolves to," not the parsedresponse.valueshape that issue #1703 is about. Hardcoding that callback's return type tostringpredates this PR and isn't something this change touches — I only added the generic to the non-streaming (streamer === false) branch.That said, I think your suggestion is a reasonable extension: expose the same
<T>on the streaming signature so callers ofsdk.stream.run_inline_query<T>(...)aren't stuck withPromise<string>either. I'd rather do that as a deliberate follow-up (along with the otherresult_format-driven methods called out in the PR description —run_query,run_look, etc.) once the core generic-default pattern here is confirmed to be the right approach, rather than widen this PR's diff. Let me know if you'd prefer it bundled in now instead.