Any ideas when the linting is this going to be fixed? We're on 3.52.2
Hi @peter.b, we definitely still have linting issues both on Apps and Workflows. In order to add your feedback to our internal bug report, could you share where is the current_user object is showing as undefined?
Hey @peter.b, here is an update on this issue:
The linting bugs have improved significantly on cloud but those changes haven't made it to the Self-hosted stable releases yet. They are available on edge releases 3.58.0+. We plan to include all current fixes in the next stable release (tentative date 8/27). On the meantime, we could upgrade to edge releases.
Hi Peter,
I don't know if this is related but I get lots of 'not defined' errors upon start up of the application and then as the app progresses and queries are run they tend to go away.
I find that putting annoying checking code in the query (if x ? 'something' : null) will often fix it although I have mostly given up on that and ignored the linter. I don't know what else to do.
Our new stable release, version 3.75, includes a fix for the linter errors. 
1 Like
Hope so,
We are on Prem so dont have access to that release just yet - we were 'promised' linting had been fixed in 3.52.14 (our current version) but. apparently not
I'm sorry we provided you with wrong expectations about the fix for this issue. It's much more complex than it looks. Much progress has been made but there is still more work to do before the linter errors are gone for good.
I'm testing on 3.75-stable and it looks like the ones related to the current_user, lodash, and formatDataAsArray are gone.
Hi @Paulo - not sure if this is the place to bring it up or if I should open up another thread, but linting in multipage apps seems totally broken. I am getting linting errors for items which are not in scope for the code which is not in scope for the page I am viewing, and most of it seems to be that the code is referencing out of scope elements. Is this known/being worked on?
2 Likes
Hi @jg80, this is definitely the right place.
I'm having a hard time visualizing this. Could you share a screenshot showing the code?
Simplest way that I think I can show it:
Create a new App with two pages: defaultPage and pageOutOfScope. Add a couple of random components and code the "pageOutOfScope" (for some reason, the linter shows already shows 1 issue, but no detail for the "issue"):
Then go back to the "defaultPage" and the linter shows an error for code which is not in scope for the page related to a component which is not in scope for the page:
We recently upgraded to 3.75.14 and linitng is now worse than it was on 3.52.14.
Pete
Thanks for expanding on your experience!
I did the above, and although I don't see errors on the defaultPage:
I do see the lining errors when I go back to the outOfScope page despite the fact that those components do exist:
However, I did find another report of exactly what you are describing. Could you attach the JSON export of your app here or DM it to me? I would love to add it to the internal report.
Export attached - sorry for the long delay!
Untitled.json (26.1 KB)
Thanks for being so patient and apologies for the confusion! As of v3.135.0 the linting tab should be fixed without any errors listed, on any multipage app.
Please let me know if you still see issues after upgrading!
Thanks,
Lam
1 Like
Thank you, Lam! So far, so good.