Skip to content

[COPILOT] fix for E1111 and numbering check / fix #736

@mcm1957

Description

@mcm1957

Description of task

Please modify logic for E1111 and W1111.

Both errors / warnings must not be raised if the corrsponding key (i.e options1) is used

  • within index.html or index_m.html if one of the exists in directory admin
  • as a key for an object within a jsonConfig definition file (admin/jsonConfig.json or admin/jsonConfig.json5).

Please note that the usage must be determined by scanning the referenced files. So maybe the complete check must be moved into M500_code module.

In addition correct numbering of W1111 and check all Error, Warning and Suggestion numbers to be in range, The error / warning / suggestion number MUST match the numbering range of the file in which the exception is created. You can calculate the valid range from the filename, i.e. M7000 indicates that this file may contain errors / warnings / suggestions startin with 7000 and up to the number of the next file. Typically 999 valid numbers exist per file, but M5000_code has only 499 valid numbers as the next file starts with M5500...

Metadata

Metadata

Labels

TRIAGEThis issue has not yet been reviewed.copilotIssue with instructions for copilot only

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions