fix: support native array methods on collections

[AayushSaini101]

closes: #874

Summary

• Fix native Array methods (.map(), .filter(), .slice()) on Collection subclasses such as SecurityRequirements
• Root cause: Array transforms construct results via the subclass constructor with a length number; Collection then does super(...collections) and throws
• Fix: set Symbol.species to Array so transforms return plain arrays (same pattern as all() / filterBy())

Problem

securityRequirements.forEach(...) // works
securityRequirements.map(...)     // throws
// TypeError: Spread syntax requires ...iterable[Symbol.iterator] to be a function

Workaround today: securityRequirements.all().map(...).

This affects every Collection subclass (Servers, Channels, Messages, SecurityRequirements, …), not only security.

Solution

In packages/parser/src/models/collection.ts:

static get [Symbol.species]() {
  return Array;
}

Native transforms no longer reconstruct a Collection with an invalid constructor signature.

Test plan

• collection.spec.ts — .map() / .filter() / .slice() return plain arrays; source/meta() unchanged
• security-requirements.spec.ts — .map() does not throw (issue reproduction)
• Existing Collection helpers (all, filterBy, get, has) still pass
• CI green on PR

Changeset

Patch for @asyncapi/parser: fix: support native array methods on collections

References

• Closes javascript map() function doesn't work on SecurityRequirements object. #874
• Related: fix: support native array methods on collections #1214

[changeset-bot]

🦋 Changeset detected

Latest commit: cf16e8b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@asyncapi/parser	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[sonarqubecloud]

❌ The last analysis has failed.

See analysis details on SonarQube Cloud

[aeworxet]

@asyncapi/microgrant_team