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

[nsteblay]

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

[awalters141]

I am also encountering this bug. It makes it difficult to diagnose any errors when I have to sort through dozens of errors constantly.

[kolorado]

We are seeing the same issue in a slightly different scenario.

In our case, the problem occurs when a Table V2 is intentionally bound to an empty dataset ([]) (e.g. before an import, or when there are simply no records to display). The application behaves correctly and shows "No records to show", but the linter reports currentRow is not defined (or field-specific errors such as comments is not defined) for every computed column.

As soon as the table contains at least one row, all linter errors disappear.

This makes the linter unreliable because legitimate empty-table states generate many false-positive errors, making it difficult to spot genuine problems.