#Checking errors doesn't seem to work?

1 messages · Page 1 of 1 (latest)

thin mortar
#

Hey, I have an example where agent said there are no errors in a file but obviously class wasn't imported.

maiden lion
#

Is this as of 1.21.8?

#

Can you try upgrading and seeing if this shows up again? we recently fixed a bug here

thin mortar
#

oh I tried it on 1.21.7, didn't notice the update, gonna try it

near silo
#

Hey, i just noticed the issue still exists. For example:

-# IntelliJ 2025.2.4, Plugin v1.25.3/v1.25.4

maiden lion
#

I think this is a JetBrains issue with error checking - let me confirm. Thanks for reporting this again!

night spade
#

Hello Henrik3, thanks for reporting this!

The root cause is that internally Intellij reports the "Invalid use of eval" as an INFO/WARNING severity error instead or an ERROR severity level error. We will add a check for this edge case and this will be fixed in the next release of Sweep!

near silo
#

Well interesting, as it's shown as an error in the UI, but i mean it's JetBrains, i don't have any expectations after the last few updates anymore lostface
I just tried with some other kind of issue as well to make sure it's not only a TypeScript issue (as i saw the same behaviour yesterday with some rust components but it didn't catch my attention first).
Could this be the same issue? If so, i would try it with the patch and report if's resolved after ^^

night spade
#

Yeah the issue is that in the UI it is shown as an error (red) but in code it is assigned INFO level.

Thanks for bringing these issues to my attention I will take a look at these

near silo
#

Hey, so for the Rust Part this seems to be resolved with 1.25.5, for TypeScript i still see the behaviour from yesterday. However thanks again for looking into this ^^

night spade
#

Yeah for Typescript the fix is alot more difficult as Intellij relies on External Annotators from bundled plugins to surface those errors. We currently do not pull those errors down but we have this planned

near silo
#

Alright ^^

night spade
#

Hello, the issue with Webstorm/Typescript should be fixed in the next release!