InvalidConfig

Summary

Validate the configuration file StyleChecker.xml.

Default severity

Error

Description

This is not a rule. The InvalidConfig analyzer validates StyleChecker.xml and reports the errors. Some typical errors are described below.

§ Not a well-formed XML document

Unexpected end of file has occurred. The following elements are not closed: element. Line n, position m.

The element is not closed.

§ Not valid for the Schema

unexpected node type: Element of the element 'unexpected' (it is expected that the element 'expected' starts)

The root element is not config, or the specified XML namespace is not "https://maroontress.com/StyleChecker/config.v1".

unexpected node type: Element of the element 'unexpected' (it is expected that the element 'expected' ends)

The unexpected element occurred.

§ ByteOrderMark element

invalid integer value of maxDepth attribute: '...'

The maxDepth attribute of the ByteOrderMark element does not have an integer value, or int cannot represent the value.

non-positive integer value of maxDepth attribute: '...'

The maxDepth attribute of the ByteOrderMark element has zero or a negative integer value.

§ LongLine element

invalid integer value of maxLineLength attribute: '...'

The maxLineLength attribute of the LongLine element does not have an integer value, or int cannot represent the value.

non-positive integer value of maxLineLength attribute: '...'

The maxLineLength attribute of the LongLine element has zero or a negative integer value.

§ NoDocumentation element

invalid boolean value of 'inclusive' attribute: '...'

The inclusive attribute of the with element does not have a boolean value. (It is possible to specify any one of the following values: true, false, 1, 0.)

Code fix

The code fix is not provided.