[MICROGRANT] Set of issues for resolution under the Microgrant Program 2026-08

[AayushSaini101]

#874
#1066

[wuyunxi]

Hi! I would like to work on this issue under the 2026 Microgrant Program.

My proposed approach is:

1. Add regression coverage for both v2 and v3 SecurityRequirements showing that native non-mutating array methods such as .map() do not throw and return the expected mapped values.
2. Fix the behavior centrally in the base Collection model. The current failure appears to come from Array species construction: Array.prototype.map() constructs the result through the derived class and passes a numeric length, while Collection expects an iterable collection. I would first validate that returning the native Array species is consistent with the intended public API, then use that minimal fix instead of special-casing SecurityRequirements.
3. Run the parser unit tests, build, lint, and any existing collection/model suites to check that other Collection subclasses keep their documented behavior.
4. Keep the change narrowly scoped and document any observable return-type behavior uncovered by the tests.

One scope question before assignment: #1204 also includes #753, but #753 was automatically closed as stale on 2024-07-27 and has no linked fixing PR. Should this microgrant reopen/retain #753, replace it, or proceed with #874 only?

I will not start implementation or open a PR until a maintainer assigns the microgrant, per the program rules.

[justanotherperson00]

Hi! I would like to be considered for this issue under the 2026 Microgrant Program.

My proposed approach would be:

1. Reproduce javascript map() function doesn't work on SecurityRequirements object. #874 with focused regression tests covering both AsyncAPI v2 and v3 SecurityRequirements collections.

2. Verify whether native Array methods are invoking the derived Collection constructor with a numeric length, causing the constructor to spread a non-iterable value.

3. Compare the compatibility implications of:

   • defining Symbol.species so native transformations return plain arrays; and
   • making the shared Collection constructor safely handle native Array construction while preserving intended collection behavior and metadata.

4. Implement the smallest centralized fix that preserves the intended public API rather than patching only SecurityRequirements.

5. Add coverage for map() and related non-mutating Array methods such as filter() and slice() where they exercise the same construction path. I would also test at least one additional Collection subclass to confirm the behavior is not specific to security requirements.

6. Run the parser unit tests, build, lint, and any browser-related checks requested by the maintainers.

Before assignment, could you clarify the intended scope of #1204? It also lists #753, which is currently closed as stale/not planned. Should that issue be reopened and included, replaced, or removed from this microgrant?

Could you also confirm:

• the final reward for the approved scope;
• whether native transformation methods are expected to return plain arrays or parser Collection subclasses; and
• the expected deadline for the assigned work?

I will not begin implementation or submit a pull request unless I am explicitly assigned the microgrant.

[pvurda]

Hi, I’d like to be considered for #1204 under the August 2026
Microgrant Program.

I agree with the diagnosis already discussed around Array species
construction. My focus would be on resolving the compatibility question
before selecting the implementation:

1. Characterize the current public behavior of Collection subclasses,
   including constructor inputs, instanceof expectations, metadata, and
   return types from native Array methods.
2. Add regression tests for javascript map() function doesn't work on SecurityRequirements object. #874 across AsyncAPI v2/v3 and more than one
   Collection subclass.
3. Compare an Array Symbol.species override with constructor compatibility
   for numeric-length construction, then choose the smallest change that
   preserves the documented API.
4. Cover map(), filter(), slice(), iteration, all(), and filterBy(), and run
   the repository’s complete validation suite.

I can also investigate #753 independently once maintainers confirm whether
it remains part of the funded scope, since it appears unrelated to #874
and is currently closed.

I will wait for explicit assignment before implementing or opening a PR.

[aeworxet]

Microgrant Issue's service comment

Text labels: microgrant/2026-08, microgrant/medium, microgrant/coding
First assignment to regular contributors: 2026-08-02 00:00:00 UTC+12:00
End Of Life after: 2026-08-31 23:59:59 UTC-12:00

@asyncapi/microgrant_team

The Microgrant Program is not a Mentorship Program. The accepted level of Microgrant Program Participants is Middle/Senior.

Regular contributors should explain in clear terms how they will approach the resolution process when expressing interest in working on this Microgrant Issue.

References: Microgrant Program 101, Microgrant Program Rules

[Jannik-cmyk]

Hi, I’d like to work on #1204 as part of the August 2026 Microgrant Program.

I’ve read through both linked issues and looked at the relevant code on the current master branch. For #753, my first step would be to reproduce the original whitespace case before changing anything. The fix from #1133 already removed the "uri-reference" restriction that seems to have caused the original diagnostic, and the pointer-decoding path should handle both raw spaces and "%20". I’d turn the original report into regression tests for AsyncAPI v2 and v3, using both YAML and object input. If the issue already passes on master, I’d keep the change limited to proper regression coverage rather than adding another normalization or resolver workaround.

For #874, the problem seems to come from native Array methods constructing their result through the derived "Collection" constructor with a numeric length. Since that constructor expects an iterable, methods such as "map()", "filter()", "slice()", "concat()", "flat()" and "flatMap()" can fail in the same way.

My preferred fix would be to define the Array species centrally on the base "Collection", so these transformation methods return normal arrays. That seems safer than allowing numeric construction, because "map()" can return completely different value types. For example, mapping a "SecurityRequirements" collection to strings should produce a "string[]", not a "SecurityRequirements" instance containing strings while its own methods still expect parser model objects.

I’d add regression tests for both v2 and v3 security requirements, test another unrelated collection subclass, and verify that existing behavior such as iteration, "forEach()", "all()", "get()", "has()", "filterBy()" and metadata on the original collection remains unchanged.

After the focused tests, I’d run the parser unit suite, lint, the ESM and CJS builds, and the browser tests. I’d also include the required changeset and provide regular progress updates.

I’d be happy to take this on and can get started as soon as it’s assigned.

[AayushSaini101]

I will be working on this issue thanks cc: @aeworxet

[aeworxet]

Following the expression of interest in working on this Microgrant Issue, @AayushSaini101 (githubID: 60972989) is an AsyncAPI Maintainer specified in the file https://github.com/asyncapi/community/blob/master/MAINTAINERS.yaml, so they fall under the first category in the prioritization list.

[aeworxet]

Microgrant Issue's Assigned Timeline

Complexity Level	Assignment Date (by GitHub)	Start Date (by MP Rules)	End Date (by MP Rules)	Draft PR Submission	Final PR Merge Start	Final PR Merge End
Medium	2026-07-29	2026-08-03	2026-09-13	2026-08-16	2026-08-30	2026-09-13

Please note that the dates given represent deadlines, not specific dates; so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

Assignee: @AayushSaini101 (githubID: 60972989)

[AayushSaini101]

@aeworxet after evaluating #753 this enhancement is not appropriate for the release, removing this from this bounty issue and adding new one from the unused Microgrant issue