On prem V3.114.16
We recently upgraded to the above version
Despite resassurances that linting will be fixed, it's still flaky and unreliable.
Hey @peter.b - keeping the linter up to date is a constant battle, to be sure, but it should be a somewhat simpler task now that we won't be maintaining a distinct context for legacy single page apps.
It's worth noting, as well, that these kind of bugfixes aren't always backported to older releases, meaning you won't necessarily see an improvement without upgrading. Is there a particular issue that you're experiencing?
It's basic and it still doesnt work:
attached screenshot of a typical example we face every day - you can clearly see the text called 'proposalTitle' exists, yet linting says it doesnt!
Tired of it tbh and all the response we ever get is ' have you upgraded" we have been promised linting will be fixed what seems like foreverover! We are on V3.114.16 (recently upgraded) still the linting is as awful as before!
Thanks for sharing a specific example. Is this a multipage app, out of curiosity? And is the textInput component that you're referencing on the main canvas or in a modal? It might be helpful to get a JSON export of your app, just to better understand its architecture.
In the meantime, I'll highlight this behavior to the team and let you know what I hear. 
Hey @peter.b - just to rule out scoping issues as the root cause of this, would you mind sharing a JSON export of your app?
Hi
It isn’t limited to any specific app . The linting is failing to work reliably on every app we have. It’s been this way regardless of updates, upgrades it’s just awful and unreliable.
It’s consistently bad so we now just got used to it and generally ignore it, checking our own declarations as we go.
1 Like
Got it - I'll keep this topic open and provide an update whenever there are specific changes or fixes to linting issues, especially around variable references.