Add regression tests for already-fixed issues #251 and #277 - #411
Merged
jemacineiras merged 2 commits intoAug 16, 2026
Merged
Conversation
This was referenced Aug 16, 2026
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 4 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
jemacineiras
previously approved these changes
Aug 16, 2026
jemacineiras
approved these changes
Aug 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds regression tests that confirm two previously-reported issues are already resolved on current
main(they were fixed indirectly by later refactors; reported against much older versions).Closes #251
Closes #277
#251 — [OpenApi] API code not generated when a
$refpath parameter has no description (reported on 4.8.5)New end-to-end fixture
testNoDescriptionRefParameterGenerationuses the exact spec from the issue (/test/{testId}with a$refto#/components/parameters/testId, nodescription, response$refto#/components/responses/TestResponse). It asserts the API file is generated with the@PathVariableparameter.#277 — [AsyncAPI] custom validators only generated in one model package when consumer/supplier use different
modelPackageNew fixture
testCustomValidatorsDifferentPackagesconfigures the consumer and supplier with differentmodelPackages, both referencing the same schema (data) that has constraints (required, min/max, pattern, size). It asserts thecustomvalidatorfolder is generated with the full set of annotation + validator classes in both the consumer and producer packages, and that eachDataDTOimports them from its own package.Validation
multiapi-engine: full suite green — 133 tests, 0 failures (was 131 before these two cases).