-
Notifications
You must be signed in to change notification settings - Fork 2.3k
SwaggerEditor@next: use more appropriate fixtures #3627
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
Comments
@ponelat @char0n |
In UI text, consider using "example" or a similar common word instead of "fixture". If the menu component supports submenus / nested menus, I would suggest moving those items to the "File" menu:
|
This issue is about making the move now, so that we use standard industry recognized fixtures.
ADS has full support in ApiDOM and we also created renderer that can render it. It's currently the only implementation out there.
There is no official OPAS 3.1 fixture. The plan is to construct one from OpenAPI 3.0 @hkosova fully agree, updating my proposal. |
To clean up the examples (fka fixtures) sounds good. |
Linking OpenAPI issue I've created to track the OpenAPI 3.1.0 Petstore effort: OAI/learn.openapis.org#98 |
Examples now don't contain any dev related fixtures. Refs #3627
NOTE: I've constructed OpenAPI 3.1 example from 3.0 version. When OAI/learn.openapis.org#98 is processed, I'll update the OpenAPI 3.1 example in SwaggerEditor@next to reflect the official OpenAPI 3.1 Petstore one. |
Creation of idiomatic OpenAPI 3.1 Petstore fixture has been deferred to #3744 |
Examples now don't contain any dev related fixtures. Refs #3627
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem?
Our current fixtures that editor can load, are a little bit chaotic. Here is how it looks today:
Here is the examples of what some of the menu items load:
Load OpenAPI 3.0 fixture
Load OpenAPI 2.0 fixture
Load OpenAPI 3.1 fixture
Describe the solution you'd like
I'd like to propose more sensible and expected fixtures. All fixtures will load in
YAML format
. Fixture will either be standard petstore one provided by OpenAPI or AsyncAPI initiative or our own SmartBear used one. @hkosova also proposed to amend the nomenclature -fixture
-example
and move underFile
menu into submenu (if possible) - I fully support this suggestion and incorporated into this proposal.<separator>
<separator>
<separator>
Describe alternatives you've considered
Leaving the status quo, but IMHO we don't provide very good fixtures.
The text was updated successfully, but these errors were encountered: