config(amazonq): disable inline tutorial since it's taking ~250ms for all users no matter it's shown or not #7722
Conversation
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
…s no matter it's shown or not
|
Will-ShaoHua
changed the title
Will-ShaoHua
commented
Jul 20, 2025
| const isInlineEdit = result.items.some((item) => item.isInlineEdit) | ||
|
|
||
| // TODO: question, is it possible that the first request returns empty suggestion but has non-empty next token? | ||
| if (result.partialResultToken) { |
Contributor
Author
There was a problem hiding this comment.
in other words, should it be
if (result.suggestions.length && result.partialResultToken) {
// pull subsequent suggeestions
}
Contributor
Author
|
/retryBuilds |
leigaol
approved these changes
Jul 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…
Problem
by design, the code path should only be applied to "new" users, however currently it's taking 250ms for all users no matter the UI is displayed or not.
Solution
feature/xbranches will not be squash-merged at release time.