[Bug]: Persistent Linting Errors

[samiphoenix84]

Is there an existing issue for this?

• [X] I have searched the existing issues

Description

I am continuously getting linting errors on various widgets. They do not affect the function of the app but are very annoying during development. I previously raised this bug and was told the fix was to clone the page and delete the original page. But this is not working, the linting errors keep coming back.

Steps To Reproduce

1. Create a new text input widget.
2. Add an action to run a query for the 'OnSubmit' action
3. Edit the 'OnSubmit' action and delete the action to run the query.
4. You will now see a linting error on the widget.

See video for demo

Public Sample App

No response

Environment

Production

Severity

Medium (Frustrating UX)

Issue video log

https://www.loom.com/share/664e7030e2cd4debb2cdf4b8c7e82d1d?sid=b3617fe6-2367-4997-b667-3b2cd4e68fa1

Version

Cloud

[samiphoenix84]

Is this going to be fixed any time soon?

[SPX84]

When will this bug to be fixed please?

[virgilio-lattanzi]

Confirming that this issue is still present in Appsmith v1.80 (Docker Community Edition).

I can reproduce it consistently by inserting a JS line comment (// comment) at the beginning of any event field (onClick, onTextChange, onCheckChange, etc), after the {{ Once the error appears (Expected an identifier and instead saw ';'), it remains even after clearing the field, and only goes away by inserting a valid dummy expression like {{0}} or {{true}}.

This affects any widget, not just TextInput. The Linter seems to get stuck after encountering malformed or commented expressions in event fields.

Tested on multiple widgets in a clean install. Hope this helps clarify the scope of the issue.

[wawa79]

Confirming that this issue is still present in Appsmith v1.80 (Docker Community Edition).

I can reproduce it consistently by inserting a JS line comment (// comment) at the beginning of any event field (onClick, onTextChange, onCheckChange, etc), after the {{ Once the error appears (Expected an identifier and instead saw ';'), it remains even after clearing the field, and only goes away by inserting a valid dummy expression like {{0}} or {{true}}.

This affects any widget, not just TextInput. The Linter seems to get stuck after encountering malformed or commented expressions in event fields.

Tested on multiple widgets in a clean install. Hope this helps clarify the scope of the issue.

Running AppSmith 1.8 Community and also fighting against that spam linting message. You made my day! Setting {{true}} to some events (those where the code was set and cleared after) clears the error for the complaining widget. But a fix would be definitely appreciated

[bunniico]

Adding then removing an 'event' from a widget seems to create this issue. Setting the widget to 'Visible = false' also gets rid of the errors.

[LeonardoRodriSilva]

I am getting this error in my application too, and it is very unsatisfactory because my company wants the best and is strange to explain the appsmith have a bug and I cannot do anything about