I just updated from 1.56 to 1.79. With no code changes Linter is now throwing multiple "currentRow is not defined" errors though no code changes have been made. This is due to tables that depend on data being available in other tables. The error occurs because data doesn't exist yet due to the fact that the dependent components haven't been accessed and activated. Once the components are activated the errors go away. The application is still running fine but these are phantom errors and make it difficult to work with the development UI.
#Pervasive currentRow error on latest release
long birch
west pecanBOT
{?{ currentRow ? currentRow['columnName'] : 'Default Value' }?}
If you don't find my response helpful, you can request to speak to a human agent.
west pecanBOT
Could you please share some screenshots with examples?
long birch
No point is sharing screen shots. Linter will list the tables and then the error I already shared. I'm not finding the responses helpful.
I submitted a Bug in Github also.
west pecanBOT
Thank you for submitting a bug report on GitHub. Your feedback is valuable, and the development team will look into it. If you need further assistance or have any other questions, feel free to ask.
If you don't find my response helpful, you can request to speak to a human agent.
tough sparrow
Sharing screenshots is always helpful. For example, I have seen a case where the table rows were collapsed in the editor and this caused the issue that you are describing.