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

Cody: Open files in workspace #53069

Merged
merged 4 commits into from
Jun 7, 2023
Merged

Cody: Open files in workspace #53069

merged 4 commits into from
Jun 7, 2023

Conversation

abeatrix
Copy link
Contributor

@abeatrix abeatrix commented Jun 7, 2023

Close #52863

Loom: https://www.loom.com/share/62c920c3c2e94d67b2f6266689a2e4fc

Open validated file paths from Cody's response as workspace file, excluding directories (opening a path to directory would create a new workspace for the directory).

path

Test plan

Locally tested. All tests have passed. See video:

Cody_.Open.non-hallucinated.file.paths.in.workspace.mp4

@abeatrix abeatrix requested review from jdorfman and a team June 7, 2023 08:58
@cla-bot cla-bot bot added the cla-signed label Jun 7, 2023
@abeatrix abeatrix marked this pull request as ready for review June 7, 2023 13:51
@sourcegraph-bot
Copy link
Contributor

sourcegraph-bot commented Jun 7, 2023

📖 Storybook live preview

Copy link
Contributor

@philipp-spiess philipp-spiess left a comment

Choose a reason for hiding this comment

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

We have an issue where sometimes paths are detected inside single backtick inline code blocks which means that it will escape the HTML tag which renders oddly.

Basically like this `foo <span blabla>bar/quz</span>`

I am worried that adding more HTML will make this experience worse. On the other hand, it works for 80% of the cases and there, not being able to click it is really bad, so let's go ahead with it.

@toolmantim
Copy link
Contributor

Does this make #52029 redundant? There's been some design improvements on there…

@abeatrix
Copy link
Contributor Author

abeatrix commented Jun 7, 2023

We have an issue where sometimes paths are detected inside single backtick inline code blocks which means that it will escape the HTML tag which renders oddly.

Oh that's a good thing to know. I will keep this in mind and yea let's go ahead with this and get more feedback before we decide how to improve this! Thanks for the review!

@abeatrix abeatrix merged commit 28959a4 into main Jun 7, 2023
25 of 26 checks passed
@abeatrix abeatrix deleted the bee/cody-file-path branch June 7, 2023 14:35
@abeatrix
Copy link
Contributor Author

abeatrix commented Jun 7, 2023

Does this make #52029 redundant? There's been some design improvements on there…

I didn't change anything regarding the styles so it'd be nice to have your changes too! The style for the hallucinated path in your PR looks so cute :D

ErikaRS pushed a commit that referenced this pull request Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cody vscode: make file paths and function names clickable
4 participants