-
Notifications
You must be signed in to change notification settings - Fork 23
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
Implement lenses using codeVision package #2318
Conversation
fdfe93e
to
7617f0c
Compare
6c3e55a
to
c17ea15
Compare
c17ea15
to
f5a7aa8
Compare
hasLensAppeared | ||
} | ||
} | ||
fun runAndWaitForCleanState(actionIdToRun: String) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need runAndWaitForCleanState
? we could use runAndWaitForLenses
directly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could, but it is not obvious that runAndWaitForLenses(actionIdToRun)
wait for no lenses to be visible anymore.
Or maybe I should change name of this function?
@@ -21,93 +19,65 @@ import org.junit.runner.RunWith | |||
@RunWith(CustomJunitClassRunner::class) | |||
class DocumentCodeTest : CodyIntegrationTextFixture() { | |||
|
|||
@Test | |||
@Ignore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so it still fails, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the way it is written there is no way it could be stable, as there is race in the test itself.
I will try to rewrite it a bit.
I encountered this one: Stacktrace:
|
c956fc2
to
b41fd1b
Compare
gradle.properties
Outdated
@@ -24,4 +24,4 @@ kotlin.daemon.jvmargs=-Xmx2g -Xms500m | |||
nodeBinaries.commit=8755ae4c05fd476cd23f2972049111ba436c86d4 | |||
nodeBinaries.version=v20.12.2 | |||
cody.autocomplete.enableFormatting=true | |||
cody.commit=daa1693620fdf2784ecd190dd12bb07169950a90 | |||
cody.commit=5bd253c16261680490d2afb14398ff568334ffbd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need to update the cody commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not needed.
I had some problems which I thought were related to bugs in cody main but it turned out to not be the case.
I reverted this change for now.
But we should update it. I will do it in a separate PR.
b41fd1b
to
48e9346
Compare
Enterprise account signed in, there is an error:
|
it looks like the model / apiversion problems are resolved in the latest main in cody |
however, it looks like the lenses does not work while indexing. maybe we should simple NOT make any lens-using action dumb aware? |
6d3150c
to
529d880
Compare
It is other way around, But in our case problem are not the actions but |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm with the latest changes in cody
Fixes CODY-3743
Changes
New implementation of code lenses using IntelliJ codeVision package.
Unfortunately the way JetBrains implemented codeVision providers is such that only one item of a given provider can be displayed per line. That forced me to create distinct provider for every code lens action we want to support. That said it's not a bit problem, I made sure that all of them have shared configuration:
Test plan
Full QA of all edit commands is required.