false negatives on type properties on custom objects

[JustFly1984]

Hello @deepcodeg
I have a lot of false negatives on "type" fields of custom objects in my typescript code, and ignore comments do not resolve it.

even in redux reducer (immer)

Thank you for great plugin, it improves development experience.

[JustFly1984]

one more issue I have found:

cy.get() returns promise-like object, not the promise, so it has no catch chaining.
I already have an eslint ignore next line comment.

The issue is If I'm adding deepcode ignore comment, it disables functionality of eslint comment by moving it up. Can deepcode interoperate with eslint?

[Arvi3d]

Hello @JustFly1984, thank you for you feedback. We managed to reproduce this issue and will work on fixing it and update you once it's done.

As for linter. We have a non-documented way. Pls try to add deepcode's comment in the same line or below. Our engine should catch it.

[JustFly1984]

@Arvi3d I do not really want to bloat the codebase with comments, cos it is around 300+ warnings, and I better wait till it will be fixed on your side. Thank you!

[JustFly1984]

@Arvi3d I've got a bunch of new false negatives for you today:

• 1

here it is a clearly bug, somehow it thinks that {count >= 10 ? '9+' : count} is variable assignment, btw to const, which should be illegal in first place, so later in the code it thinks that count is type of string with value "9+"

• 2

here it thinks that Set is not used, but it is used in for of cycle.

• 3
  And I constantly see connection errors, and it heats my macbook pro pretty hard:

so I've disabled it again for a while.

[JustFly1984]

Currently I confirm bugs fixed, except PromiseLike (without catch) for cypress, and string literal "9+"