Provide a warning when detecting the use of an undeclared macro.

[tmoody]

Please can the linter report if an undeclared macro had been used?

Declared macros are considered to be:

• built-in SAS macros such as %scan, %index, %trim, etc
• macros that are already named under the <h4> SAS Macros </h4> section of a job's header
• declared within the job itself (including via <h4> SAS Includes </h4>)

SAS Macro keywords (such as %if,%then, and %do) should not trigger the rule.

It is accepted that macros made available to a job through the SASAUTOS system option will trigger false positives.

[allanbowe]

Similar to #212 this is not something that would always "work" given that the linter can only assess the file in question (or surrounding files in the filesystem)

There are many cases where the macro definition could be defined outside the file in question eg, the autoexec, stpinit reference, secondary SASjs Artefacts, the SASAUTOs false positives you already mentioned.

A reasonable workaround would be that we could include an 'ignore list' on a per file, or per project basis.

On that basis, if there is funding, we would build it.