Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: permit to set spec version with property #257

Merged
merged 1 commit into from
Aug 20, 2024

Conversation

ndr-brt
Copy link
Member

@ndr-brt ndr-brt commented Aug 20, 2024

What this PR changes/adds

Permits to set the openapi spec version with an apiVersion properties.

Why it does that

currently it is not possible and it was necessary to set the whole project version, but spec and project version are (/should be) two completely different values.

Further notes

  • uniform the way with which it's possible to customize the api spec by reading also apiTitle and apiDescription that are currently evaluated in the single repo build files.
  • removed unused extension methods

Linked Issue(s)

Closes #256

Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

@ndr-brt ndr-brt added enhancement New feature or request build labels Aug 20, 2024
Copy link

github-actions bot commented Aug 20, 2024

Test Results

52 tests  ±0   52 ✅ ±0   20s ⏱️ ±0s
21 suites ±0    0 💤 ±0 
21 files   ±0    0 ❌ ±0 

Results for commit 2a98694. ± Comparison against base commit 1dbf5ea.

♻️ This comment has been updated with latest results.

@ndr-brt ndr-brt force-pushed the 256-openapi-merger-properties branch from de45cdb to 2a98694 Compare August 20, 2024 10:00
@ndr-brt ndr-brt merged commit cb190f9 into main Aug 20, 2024
17 checks passed
@ndr-brt ndr-brt deleted the 256-openapi-merger-properties branch August 20, 2024 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

improve swagger extension parameterization
2 participants