L2 config

.github/ISSUE_TEMPLATE/simple-issue-template.md

@@ -0,0 +1,92 @@
+---
+name: Simple issue template
+about: Describe this issue template's purpose here.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+---
+name: Issue simple
+about: Used to standard issue in simple format.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+---
+name: BOC
+about: BOC Community Issues Template
+title: "[BOC] Button for likes"
+labels: BOC
+---
+
+## Description
+
+[Provide a brief description of the feature, including why it is needed and what it will accomplish. You can skip any of Goals, Expected Outcome, Implementation Details, Mockups / Wireframes if they are irrelevant. Please note that this section of the ticket is suggestive & you can structure it as per your prerogative.]
+
+## Goals
+
+- [ ] [Goal 1]
+- [ ] [Goal 2]
+- [ ] [Goal 3]
+- [ ] [Goal 4]
+- [ ] [Goal 5]
+
+## Expected Outcome
+
+[Describe in detail what the final product or result should look like and how it should behave.]
+
+## Acceptance Criteria
+
+- [ ] [Criteria 1]
+- [ ] [Criteria 2]
+- [ ] [Criteria 3]
+- [ ] [Criteria 4]
+- [ ] [Criteria 5]
+
+## Implementation Details
+
+[List any technical details about the proposed implementation, including any specific technologies that will be used.]
+
+## Mockups / Wireframes
+
+[Include links to any visual aids, mockups, wireframes, or diagrams that help illustrate what the final product should look like. This is not always necessary, but can be very helpful in many cases.]
+
+---
+
+[Please note that the below section of the ticket ****has to be in the format as mentioned as it is key to enabling proper listing of the project.**** Please only choose the options mentioned under the headings wherever applicable.]
+
+### Product Name
+
+[Product Name: For eg: Beckn, Sunbird Obsrv etc]
+
+### Project Name
+
+[Project Name: Descriptive of the ticket]
+
+### Organization Name:
+
+[Organization Name]
+
+### Domain
+
+[Area of governance]
+
+### Tech Skills Needed:
+
+[Required technical skills for the project]
+
+### Complexity
+
+Pick one of [High]/[Medium]/[Low]
+
+### Category
+
+Pick one or more of [CI/CD], [Integrations], [Performance Improvement], [Security], [UI/UX/Design], [Bug], [Feature], [Documentation], [Deployment], [Test], [PoC]
+
+### Sub Category
+
+Pick one or more of [API], [Database], [Analytics], [Refactoring], [Data Science], [Machine Learning], [Accessibility], [Internationalization], [Localization], [Frontend], [Backend], [Mobile], [SEO], [Configuration], [Deprecation], [Breaking Change], [Maintenance], [Support], [Question], [Technical Debt], [Beginner friendly], [Research], [Reproducible], [Needs Reproduction].

api/dent.yaml

@@ -496,6 +496,7 @@ paths:
                       $ref: '#/components/schemas/Descriptor'
                   required:
                     - order_id
+                    - cancellation_reason_id
               required:
                 - context
                 - message
@@ -1903,6 +1904,10 @@ components:
         type:
           description: 'A code that describes the mode of fulfillment. This is typically set when there are multiple ways an order can be fulfilled. For example, a retail order can be fulfilled either via store pickup or a home delivery. Similarly, a medical consultation can be provided either in-person or via tele-consultation. The network policy must publish standard fulfillment type codes for the different modes of fulfillment.'
           type: string
+          enum:
+            - CHARGING
+            - AUTOMATIC-DISPATCH
+            - VIRTUAL-POWER PURCHASE-AGREEMENTS
         rateable:
           description: Whether the fulfillment can be rated or not
           type: boolean