Skip to content

[Implementations] Added editing tools section with known OpenAPI 3.0 Editors #1159

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

Merged
merged 1 commit into from
Jun 30, 2017

Conversation

tedepstein
Copy link
Contributor

Not sure if you want to include commercial tools, or just open source components. If this is only for open source tooling, you can remove the RepreZen API Studio row from the table. (Or comment on the PR, and I'll remove it.)

Not sure if you want to include commercial tools, or just open source components.  If this is only for open source tooling, you can remove the RepreZen API Studio row from the table.  (Or comment on the PR, and I'll remove it.)
@@ -20,6 +20,15 @@ These tools are not necessarily endorsed by the OAI.
| Tavis.OpenApi | [GitHub/tavis-sofware/Tavis.OpenApi](https://github.com/tavis-software/Tavis.OpenApi/) | dotnet | C# based parser with definition validation and migration support from V2 |


#### Editors

| Title | Project Link | Language |Description |
Copy link
Contributor

Choose a reason for hiding this comment

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

Is the language in which it is implemented actually relevant for an editor?

Copy link
Member

Choose a reason for hiding this comment

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

Possibly more useful would be a platform column with e.g. Eclipse or web in these cases.

@RobDolinMS
Copy link
Contributor

I wonder if the whole implementations.md file should be moved to the OpenAPI website instead of being a Markdown file on GitHub.

@fehguy
Copy link
Contributor

fehguy commented Jun 13, 2017

I always considered it a temporary solution to try to get more eyeballs on the implementations. I don't think it belongs on the OAI site because (a) it is too slow to update and (b) it may be construed as favoring a particular project. Where it is now, users (like @tedepstein did) can send a PR to get their project added.

@RobDolinMS
Copy link
Contributor

#TDC: We want to have something like this in GitHub so that TDC can add/edit (instead of public website where it may be harder or more expensive to edit.)

@RobDolinMS RobDolinMS added this to the Ancillary milestone Jun 15, 2017
@RobDolinMS RobDolinMS changed the title [Implementations] Added editors section with known OpenAPI 3.0 Editors [Implementations] Added editing tools section with known OpenAPI 3.0 Editors Jun 16, 2017
@RobDolinMS
Copy link
Contributor

#TDC: We want to include ALL tools (OSS + closed source, free + paid, etc.)

#TDC: It would be nice if the OAI website could be driven from GitHub. (RAML.org does this)

#TDC: It would also be nice to have a semi-official list of data types; maybe as a separate repo.

See #1246 for more discussion.

@RobDolinMS RobDolinMS merged commit d4d3e4f into OAI:OpenAPI.next Jun 30, 2017
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

Successfully merging this pull request may close these issues.

5 participants