Skip to content

fix: make the v7.0.0 swagger export succeed and name the entity on failure - #2951

Merged
simonredfern merged 1 commit into
OpenBankProject:developfrom
hongwei1:fix/swagger-v7-null-example
Oct 29, 2026
Merged

simonredfern merged 1 commit into
OpenBankProject:developfrom
hongwei1:fix/swagger-v7-null-example

Conversation

@hongwei1

Copy link
Copy Markdown
Contributor

GET /obp/v5.1.0/resource-docs/v7.0.0/swagger returns 200: the example of the dynamic change request response now carries an empty current_payload object, which the swagger export can describe. When an example cannot be turned into a schema, the error names the entity and field (for example DynamicChangeRequestJsonV700.current_payload), so a future occurrence can be located from the message alone. SwaggerDocsTest requests the v7.0.0 export.

Closes #2950.

…ilure

The example of the dynamic change request response no longer carries JNothing as current_payload, so GET resource-docs/v7.0.0/swagger returns 200. When an example cannot be turned into a schema, the error now names the entity and field. A scenario in SwaggerDocsTest requests the v7.0.0 export.
@sonarqubecloud

Copy link
Copy Markdown

@simonredfern
simonredfern merged commit 6800ac3 into OpenBankProject:develop Oct 29, 2026
13 checks passed
@hongwei1
hongwei1 deleted the fix/swagger-v7-null-example branch October 29, 2026 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GET /obp/v5.1.0/resource-docs/v7.0.0/swagger returns 400 OBP-50000: Example should neither be JNothing nor JNull

2 participants