Use of an Array for message.order.provider.locations in Beckn Core Protocol Spec Version 0.9.4 #411
rajaneeshk90
started this conversation in
Core Specification
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Introduction:
This discussion aims to explore the rationale behind the current design choice of utilizing an array for the message.order.provider.locations field in the beckn core protocol spec version 0.9.4. The goal is to gain a deeper understanding of the decision-making process and its implications.
Agenda:
Guidelines:
Maintain a respectful and open-minded discussion.
Focus on understanding the reasoning behind the array structure.
Context:
It is defined here: https://github.com/beckn/protocol-specifications/blob/core-0.9.4/core/v0/api/core.yaml#L1980
Discussion Points:
If we are allowing only one element in the array, we are better of with declaring it as a location object. By keeping it an array we are giving the developers and impression that they can send multiple locations in this array.
Will be happy to hear others views on it.
Thanks,
Rajaneesh
Beta Was this translation helpful? Give feedback.
All reactions