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

proposal: package name change to elysiajs/openapi #117

Open
marclave opened this issue Apr 21, 2024 · 2 comments
Open

proposal: package name change to elysiajs/openapi #117

marclave opened this issue Apr 21, 2024 · 2 comments
Assignees

Comments

@marclave
Copy link
Collaborator

marclave commented Apr 21, 2024

Swagger is version 2.0 of OpenAPI, we should promote the OpenAPI standard :) especially since OpenAPI 4.0 is being released this year!

Wanted to open a discussion about renaming or potentially having a new package release with the OpenAPI name?

Thoughts? 🤔 @SaltyAom

@SaltyAom
Copy link
Member

I support this change since Elysia the name Swagger is originally for plugin with Swagger, but now we are using Scalar and provide Swagger support as well which doesn't really reflect the name.

However, I have some other name in mind as well:

  • elysia/doc
  • elysia/documentation

I'm afraid that some people using swagger are not familiar with what OpenAPI is since many are new to backend and using Elysia as one of their first framework.

But I support moving out from Swagger name to reflect that as well, what do you think?

@marclave
Copy link
Collaborator Author

I support this change since Elysia the name Swagger is originally for plugin with Swagger, but now we are using Scalar and provide Swagger support as well which doesn't really reflect the name.

However, I have some other name in mind as well:

  • elysia/doc
  • elysia/documentation

I'm afraid that some people using swagger are not familiar with what OpenAPI is since many are new to backend and using Elysia as one of their first framework.

But I support moving out from Swagger name to reflect that as well, what do you think?

awesome! I saw your twitter poll too so im excited to see what the community has to say ✨

https://twitter.com/saltyAom/status/1783024458435092593

I think if we went for "doc" or "documentation" it might be thought as documentation for ElysiaJS vs documentation for the API youre building 🤔

OpenAPI covers both the scenario of docs + the spec generation. could do scalar also 🤔 but i think OpenAPI would be my first pick.

LiteStar conveys docs from OAS like so:
Litestar serves the documentation from the generated OpenAPI schema

what do you think @SaltyAom ? :-)

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

No branches or pull requests

2 participants