Open emmayank opened 1 month ago
Here is the sample L2Config written in Open API Specification 3.1 - https://github.com/rajaneeshk90/local-retail-rk/blob/layer2-28thJune/api/l2-config/localretail_shopping_1.1.0.yaml
Here is the Postman collection to validate against the above L2 Config
assigning this issue to @mishalabdullah
@emmayank and @harshcrop, How can I test the schema validator using the sample l2 config and the post collection provided ?
Hi @Mishalabdullah , Add the L2Config, and then make the request as given in the postman collection. for each API i have given some positive and negative cases. for negative cases you should be getting error from the validator.
Hey @emmayank this looks interesting to me, can I pick this one ?
Hi @madhukaraman, can you please go through the issue and let us know the ETA, will assign you the issue post that.
Hey @emmayank , can we get discord vc understand the repository and task better so that I can provide you the ETA.
Same with me, Any high level info would be highly appreciated.
@KPRASANT9 @madhukaraman Please review the repository and familiarize yourselves with it. We've outlined most of the details regarding what we aim to achieve in this issue. Let us know what support you need to get started.
https://github.com/cdimascio/express-openapi-validator/pull/882 : Link shared by Venkatesh - updating here.
The content in this PR is now available on branch oas-3.1 and package express-openapi-validator@6.0.0-alpha.1. please try it out.
oas-3.1
and pr-882)npm install express-openapi-validator@6.0.0-alpha.1 To contribute submit PRs against the oas-3.1 branch.
The current plugin is now supporting OAS3.1. instead of replacing the plugin we need to test if it is working fine with the current plugin
Ticket Contents
Purpose
Each network has its own policy rules that need to be validated at the protocol layer. Currently, BAP and BPP must write custom business logic to validate these policy rules, leading to increased development and maintenance overhead. Additionally, this approach creates a higher likelihood of inconsistencies at the protocol level among different participants (BAP/BPP). The purpose is to validate the policy rules specified in Level 2 (L2) configurations of Open API Specification 3.1 directly at the protocol level, thereby reducing overhead and ensuring uniformity across participants.
Objective
Following are the Objective for this goal :
Goals
Assess Middleware Compatibility:
Middleware Integration:
Configuration Validation:
Testing and Verification:
Documentation and Reporting:
Deployment and Monitoring:
Acceptance Criteria
Full Support for Open API Specification 3.1:
Latency Performance:
Documentation and Reporting:
Implementation Details
Explore this library for the validation - https://www.npmjs.com/package/openapi-backend
Product Name
Protocol Server
Domain
Validation
Tech Skills Needed
JavaScript, Node.js
Complexity
Low
Category
Backend