Adding unit test to provoke exception using Sch_WhiteSpaceRestriction…

[mrj001]

@buyaa-n
Per your suggestion in PR#33890, I'm using a second pull request.

This contains my attempt to provoke the exception using Sch_WhiteSpaceRestriction1 as its message. However, it is provoking a different exception:

I suspect this is a bug, as the XSD I'm trying to compile differs from the example in Paragraph 4.3.6 only in the name of the type and the presence of the namespace qualifier. (I'm pretty sure I've got the correct version of the spec now. :-))

The active test case is attempting to determine what was going wrong. The commented out test case is the one to actually try to provoked the exception.

Fixes #30218:

[ghost]

Tagging subscribers to this area: @buyaa-n
Notify danmosemsft if you want to be subscribed.

[mrj001]

@buyaa-n
I was not happy with my suspicion of a bug, so I kept looking at it.
I found my problem with the schema in the PR - I had a lower-case "s" in "whiteSpace". That was so hard to see, but now the error message makes sense.

[buyaa-n]

I was not happy with my suspicion of a bug, so I kept looking at it.
I found my problem with the schema in the PR - I had a lower-case "s" in "whiteSpace". That was so hard to see, but now the error message makes sense.

That happens 😄, glad that you found it, thank you for your continuous effort. seems now you need to fix the tests and resolve conflict

[mrj001]

@buyaa-n
Tests are fixed. Conflict is resolved.

This PR now covers the final 3 of the 13 string resources in Issue #30218:

• Sch_WhiteSpaceRestriction1
• Sch_WhiteSpaceRestriction
• Sch_AttributeRestrictionInvalidFromWildcard

[buyaa-n]

Thank you @mrj001, it looks great, sorry for the delayed review

[buyaa-n]

This PR now covers the final 3 of the 13 string resources in Issue #30218:

Great, then we should add fixes #30218 in the definition, so that it get closed automatically after merge

[krwq]

Thanks @mrj001!