Details

      Description

      Indeed for the time being there is one rule for each kind of error reported by Xerces but this approach has several disadvantages :

      • Rule names are meaningful as they duplicate the xerces violation messages. Example :
      Element ''{0}'' cannot have character [children], because the type''s content type is element-only
      
      • Most of the time you don't need and don't wan't to activate each kind of possible violation independently

      So the solution is to group all those violations behind the same generic rules.

        Activity

        Hide
        henryju OLD - Julien HENRY added a comment -

        I took the decision to remove this rule from Sonar Way as for me this rule should be configured to be applied for specific file extension and specific schema.

        Show
        henryju OLD - Julien HENRY added a comment - I took the decision to remove this rule from Sonar Way as for me this rule should be configured to be applied for specific file extension and specific schema.
        Hide
        freddy.mallet Freddy Mallet added a comment -

        Manually tested !

        Show
        freddy.mallet Freddy Mallet added a comment - Manually tested !

          People

          • Assignee:
            henryju OLD - Julien HENRY
            Reporter:
            freddy.mallet Freddy Mallet
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: