Many Qlik developers use external code editing platforms (Notepad++,Atom, and Visual Studio Code). There should be supported language and syntax packs for external editors, provided by Qlik. Since these rules and definitions are already built somewhere in the source code for the internal editor, they should be ported for other editing platforms.
Ideally also including a way to do an on-demand syntax check on scripts. I would love to have a CI/CD workflow that verifies the correctness (from a syntax point of view) of the code before deploying it. This would enable workflows that are pretty much the same as the workflows used by "regular" (non-qlik) developers out there, of which there are millions and millions.
My point is: If a way of working as proven effective by lots of people over many years, why shouldn't we Qlik developers also use it? Right now it's possible to do bits and pieces, but it's hard to set up a complete, good and modern developer process for Qlik scripting.
Thank you for your feedback on ways to improve our product. While this is something we understand would be useful, it's not on the short-term roadmap. Please continue to show your support for this idea.
Fyi, Matt Fryer keeps a definition file for Notepad++ here:
NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.
.png "Luminary Alumni"){kind=icon}