[Bug]: Linter is showing currrentRow errors before dependent component is activated and associated queries run

Is there an existing issue for this?

• I have searched the existing issues

Description

I have an application that has components with tables that depend on data existing in other components with tables. Linter is reporting "currentRow is not defined" errors because the dependent component has not been activated and queries run. This wasn't a problem in version 1.56 but since upgrading to 1.79 I get these false errors. The systems is working but I can't rely on the Linter any longer to present actual errors making the development UI very difficult to work with.

Steps To Reproduce

Create a component with table that is dependent on values in another component table.

Public Sample App

No response

Environment

Production

Severity

Medium (Frustrating UX)

Issue video log

No response

Version

1.79