Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Protocol-Specification Version 1.2 release

Open
#451 2 comments 0 reactions 1 assignee View on GitHub

@rajaneeshk90 is already working on this.

Since Oct 15, 2024.

Assessment

This issue has not been assessed yet.

Description

protocol-specifications
Description:

As part of the Protocol-Specification version 1.2 release, the following changes are targeted:

  1. Create a schema called Document that can be attached to any Order, Item, or Fulfillment as an array of docs: https://github.com/beckn/protocol-specifications/issues/377
  2. Need to add ItemQuantity to AddOns: https://github.com/beckn/protocol-specifications/issues/376
  3. Need to add Document array in Order Schema to transmit order-related documents: https://github.com/beckn/protocol-specifications/issues/375
  4. Required field 'return_reasons' in 'rating_categories' endpoint in meta.yaml ver 1.0.0: https://github.com/beckn/protocol-specifications/issues/355
  5. "Errors in meta.yaml core ver 1.0.0": https://github.com/beckn/protocol-specifications/issues/354
  6. "Errors in transaction.yaml core-v1.0.0": https://github.com/beckn/protocol-specifications/issues/350
  7. Typo in readme file: https://github.com/beckn/protocol-specifications/issues/348
  8. "ttl type inconsistent": https://github.com/beckn/protocol-specifications/issues/343

Other Issues which are fixed as part of this release but are not tracked using tickets.

  1. Support & on_support Schema update
  2. Price.value type changed to string from number
  3. Xinput Schema Update
  4. Payment Object schema update
Dominant language
No language data
Stars
455
Forks
127
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from beckn/protocol-specifications

All issues in beckn/protocol-specifications

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.