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

[AayushSaini101]

• Payload property named message breaks with null value #863
• Binding interface does not support excess properties #735

[justanotherperson00]

Hi! I would like to be considered for #1203 under the 2026 Microgrant Program.

My proposed approach would be:

1. For [BUG] Any non supported schema format should not make the doc invalid #1066, reproduce the unsupported custom schemaFormat behavior with focused parser tests and trace the distinction between document validation, parser-registry lookup, and schema interpretation.

2. Preserve the existing behavior of built-in and registered custom schema parsers while ensuring that an unsupported but valid string format does not, by itself, invalidate the complete AsyncAPI document.

3. Review the earlier [BUG] Any non supported schema format should not make the doc invalid #1066 implementation attempts before choosing the result representation. I would confirm with the maintainers whether unsupported schemas should preserve raw schema data and format metadata, remain intentionally unresolved, or use another established model behavior rather than silently defining a new public API contract.

4. For Payload property named message breaks with null value #863, reproduce the nullable payload property failure directly in parser tests, identify the rule or JSONPath predicate that reads schemaFormat from a null or unrelated property named message, and apply the narrowest type, null, path, or structural guard that preserves validation of actual AsyncAPI Message Objects.

5. Add regression coverage for unsupported string formats, invalid non-string formats, registered formats, nullable and non-null payload examples, unrelated property names, and relevant v2/v3 behavior.

6. Run the requested parser tests, browser-facing tests where applicable, build, lint, and release checks before opening a focused PR.

Before assignment, could you confirm:

• whether [MICROGRANT] Set of issues for resolution under the Microgrant Program 2026-09 #1203 includes both [BUG] Any non supported schema format should not make the doc invalid #1066 and Payload property named message breaks with null value #863;
• the intended parser/model representation for an unsupported schema format;
• the final reward and deadline; and
• whether equivalent v3 coverage is expected for Payload property named message breaks with null value #863?

I have also expressed interest in #1204. I currently have capacity to complete both microgrants if I am selected for both, subject to confirmation of their final scopes and deadlines. I would keep the work in separate focused branches and follow the required progress-update cadence for each assignment.

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

[DPS0340]

I would like to be considered for this Microgrant under the 2026-08 program. I will not start implementation or open a PR unless the parser-js maintainers explicitly assign it to me.

My proposed approach:

1. For [BUG] Any non supported schema format should not make the doc invalid #1066, first reproduce the failure with an unregistered string schemaFormat (for example, application/octet-stream) and trace the v3 schema-format validation/parser-registry boundary. I will preserve parsing for registered formats, keep invalid non-string values invalid, and add focused regression coverage for the intended representation of unsupported-but-valid formats rather than silently inventing a new public model contract.
2. For Payload property named message breaks with null value #863, add the minimal nullable payload.properties.message fixture and trace the ruleset JSONPath predicate that dereferences values named message. I will replace only the unsafe null/non-object assumption while retaining diagnostics for actual AsyncAPI Message Objects.
3. I will cover the reported cases plus nearby controls (registered format, malformed format, non-null message, and a real Message Object), then run the repository's focused tests, full test suite, lint, and build.

Before implementation, please confirm that the 2026-08 aggregate includes both #1066 and #863, and whether unsupported valid schema formats should remain raw/unresolved when no parser is registered. If selected, I will keep the changes in one focused branch and provide regular progress updates.

[AayushSaini101]

i would like to work on this issue thanks cc: @aeworxet

[aeworxet]

Microgrant Issue's service comment

Text labels: microgrant/2026-09, microgrant/medium, microgrant/coding
Assignment to regular contributors after: 2026-08-23 00:00:00 UTC+12:00
End Of Life after: 2026-09-30 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

[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-09-07	2026-10-18	2026-09-20	2026-10-04	2026-10-18

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)