fix: Adding import references in examples/customsearch #1399
Conversation
This file contains 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
Missing alias for the `customsearch` import statement will cause its references to raise errors
zalgonoise
changed the title
zalgonoise
changed the title
|
Note we can add this, but is only sugar as the package name for that import is already |
codyoss
approved these changes
Jan 18, 2022
codyoss
added
the
kokoro:force-run
kokoro-team
removed
the
kokoro:force-run
|
Thank you! |
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.
fix: Adding import references in examples/customsearch
Missing alias for the
customsearchimport statement will cause its references to raise errors. This type of package reference is also found in every other example, with similar import statements ({package}/{version})