Merged
Conversation
github-actions
bot
added
size:M
vouch:trusted
Owner
Author
|
Hmm intesting that threadID doesn't seem to be the ThreadID from t3 code need to look into which thread representation is best |
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
1 participant
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.
What Changed
Restyling the input box UI to better align with upstream
Why
The new UI has confusing and introduced artifactial drift. This was originally introduced due to some additioanl features like threadID and Kiro supported.
Validation
Tested locally
Maintenance Impact
Reduced as drift from upstream is lower
UI Changes
Main changes were that the model selection and submission box are back with in the text box and the thread ID is now inline with the workstree selection and the same format
Checklist