0056844: More Swagger spec definition fixes in org.openbravo.api

Openbravo Issue Tracking System - Retail Modules

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0056844

Retail Modules

Web POS

public

2024-10-21 12:09

2024-10-25 09:52

Reporter

adrianromero

Assigned To

ander_flores

Priority

normal

Severity

major

Reproducibility

have not tried

Status

acknowledged

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0056844: More Swagger spec definition fixes in org.openbravo.api

Description

There are several Swagger (OpenAPI) spec fixes that needs to be reviewed:

* Tax Rate (Import)
Fix "Category" field that it is currently empty it should go to "Master Data"

* Product AUM (Import)
There is a java property that overwrites this definition "alternativeUnitOfMeasure". The solution should be just remove this mapping with the confirmation of the Retail team who is the owner of this entity. See attached screenshot.

* Define strategy for fixing swagger validation issues in other API modules owned by other teams

* Good to do: Define and document tool to validate swagger 3.1.0 version files
for example: https://github.com/Redocly/redocly-cli [^] or https://github.com/stoplightio/spectral [^]

In case of redocly:
-> % npm install @redocly/openapi-cli
-> % node_modules/@redocly/openapi-cli/bin/cli.js lint --max-problems 10000 ~/business-api-master-data.json

Steps To Reproduce

Run swagger validation 3.1.0 version for generated and manual spec files

Proposed Solution

Additional Information

Tags

No tags attached.

Relationships

related to

defect

0056613

closed

adrianromero