[Bug]: Query Editor incorrectly believes there is an error and that Table's "newRow" object is "unknown"

[dmilkie]

Is there an existing issue for this?

• I have searched the existing issues

Description

When I referenece a newRow from a table, I expect the editor to know about it

Steps To Reproduce

When adding a new row to a Table, you will want to reference the new row in performing Queries. The correct object (I believe) is {{ Table1.newRow }} https://docs.appsmith.com/reference/widgets/table#newrow-object
and this Query is successful.

However, the Query editor reports:

TypeError: entityIcon InsertFishClass: "data_table.newRow" is undefined . Please fix the binding.

Public Sample App

No response

Environment

Deploy Preview

Severity

Low (Cosmetic UI issues)

Issue video log

No response

Version

Cloud

[rahulbarwal]

@dmilkie
Your assumption is correct: The correct object is {{ Table1.newRow }}
Now why do you get this error:

TypeError: entityIcon InsertFishClass: "data_table.newRow" is undefined . Please fix the binding.

• Unless you've clicked on Add new row, Table1.newRow is undefined
• Hence accessing any properties on that results in error.
• When you click on Add new row, the Table.newRow gets empty object as value {}
• Then even if values does not exist in the object, it will not throw error.

One workaround to mitigate this problem in QueryEditor is using {{(Table1.newRow || {}).property_name}}; this way it always gets the property.

Now as to why it is such and can it be fixed, we will evaluate and get back to it. This is not in top of our concerns.