The JADE 2022 release meets tomorrow’s business demands.
Sam Stokell 26/09/2018 2:34:34 PM
Another one I just thought of, a spell check would be great for literals in code
Paul Daigneault 18/11/2017 4:23:51 AM
It would also be great to see features, like unused variables or inaccessible code being grayed out.
John Richards 7/11/2017 2:25:59 PM
This is being considered as part of a larger review of the language and compiler.
Sam Stokell 3/11/2017 10:07:49 AM
Could also include Casting that is not required for example "thisIsAString.String" "customer.Customer"
FileVision UK Ltd 26/09/2017 4:09:15 AM
I think I better name for this could be "compiler warnings"
John Beaufoy 21/09/2017 2:11:33 PM
Note in the more recent versions of Jade, static analysis is available:
That said, doing it real time has a greater potential to improve the quality of our code and speed up development.
Some options to consider alongside the basic idea:
- Preferences dictate whether it?s available or not, as this may not be for everyone. Some specific warnings might be ?noise? depending on what you?re trying to do.
- Fix/FixAll hotkey options alongside the warnings - oh the pleasure!
- User hooks are made available, so there would be opportunity for us to write our own warnings. These could then be shared amongst the community, or simply used inhouse to help with internal coding standards / best practice.
'Compiler warnings' would be useful to implement the change on JEDI 145 - That is to flag something as being deprecated 'Compiler warnings' can warn you on this rather than it be a compile error.
Would be nice if this gets implemented to be able to select what warnings you want be shown in preferences.
Attachments Open full size