fix(spec-api): ignore XML declaration in validateXmlBodyEquals

[Copilot]

Since the migration from xml2js to fast-xml-parser (#10239), validateXmlBodyEquals prepends <?xml version='1.0' encoding='UTF-8'?> to plain expected strings, and fast-xml-parser (unlike xml2js) preserves that declaration as a ?xml node in the parsed output. This causes comparison failures when the actual request body omits the declaration.

Changes

• packages/spec-api/src/request-validations.ts — Add ignoreDeclaration: true to XMLParser options so declarations are stripped from both sides before comparison, restoring the semantic-equality behavior of xml2js.
• packages/spector/test/xml-validation.test.ts — Add test for the inverse path: actual body without a declaration matching an expected string (the exact scenario failing in Spector).

// Previously threw ValidationError; now passes
validateXmlBodyEquals(
  { rawBody: "<Root><a>1</a></Root>" },
  "<Root><a>1</a></Root>",
);

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/spec-api@11313

npm i https://pkg.pr.new/@typespec/spector@11313

commit: 217163d

[github-actions]

All changed packages have been documented.

• ✅ @typespec/spec-api

Show changes

@typespec/spec-api - fix ✏️

XML declarations no longer affect semantic body equality in validateXmlBodyEquals; both actual and expected XML declarations are ignored during comparison.

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension