Skip to content
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

fix: set border for chat file trees #197170

Merged
merged 2 commits into from
Nov 1, 2023
Merged

Conversation

joyceerhl
Copy link
Contributor

@joyceerhl joyceerhl enabled auto-merge (squash) November 1, 2023 20:12
@joyceerhl joyceerhl self-assigned this Nov 1, 2023
@VSCodeTriageBot VSCodeTriageBot added this to the November 2023 milestone Nov 1, 2023
@@ -526,10 +525,10 @@
gap: 6px;
}

.interactive-response-progress-tree .monaco-list,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it matter whether these are one the monaco-list or the parent? Shouldn't this just match used-context-list exactly?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I seem to recall that it was important to set it on the monaco-list, can't remember why though and it looks fine setting it on the parent element for now

@joyceerhl joyceerhl merged commit cf1f9c4 into main Nov 1, 2023
6 checks passed
@joyceerhl joyceerhl deleted the dev/joyceerhl/unnecessary-deer branch November 1, 2023 20:49
.interactive-session .chat-used-context-list {
border: 1px solid var(--vscode-chat-requestBorder);
border-radius: 4px;
padding: 4px;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This padding was intentional fwiw. It did cause some side effects for lists that scrolled though which I do want to fix.

Without it, we get this:
CleanShot 2023-11-01 at 14 11 27@2x

@github-actions github-actions bot locked and limited conversation to collaborators Dec 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants