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: add OpenAPIVersion component #9167

Merged
merged 1 commit into from
Aug 31, 2023
Merged

feat: add OpenAPIVersion component #9167

merged 1 commit into from
Aug 31, 2023

Conversation

kowalczyk-krzysztof
Copy link
Contributor

Refs SWG-8477

@char0n
Copy link
Member

char0n commented Aug 25, 2023

Hi @kowalczyk-krzysztof,

Looks good and gets the job done. I was thinking about a possible simplification in #9170

Now that we know we need to display OpenAPI version always, let's introduce a new OpenAPIVersion component instead of hacking VersionStamp which was intended originally just to display Info Object.version field. This way we'll achieve separation of concerns and allow OpenAPIVersion to be overriden by plugins, when somebody decides he/she wants to display the version in different way.

@kowalczyk-krzysztof
Copy link
Contributor Author

I agree, a separate component seems better 👍🏻
I'll change my implementation.

@kowalczyk-krzysztof kowalczyk-krzysztof force-pushed the feat/oas2-badge branch 5 times, most recently from e05a358 to f062324 Compare August 28, 2023 07:00
@kowalczyk-krzysztof kowalczyk-krzysztof changed the title feat: add oas 2.0 badge feat: add OpenAPIVersion component Aug 28, 2023
@kowalczyk-krzysztof
Copy link
Contributor Author

I changed my implementation to introduce OpenAPIVersion component.

@char0n
Copy link
Member

char0n commented Aug 31, 2023

Closing #9170 as it's been incorporated in this PR.

Copy link
Member

@char0n char0n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! THanks!

@char0n char0n merged commit 4b48e36 into master Aug 31, 2023
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants