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

Make schema an npm/bower module and publish is independently #137

Closed
mohsen1 opened this issue Sep 30, 2014 · 6 comments
Closed

Make schema an npm/bower module and publish is independently #137

mohsen1 opened this issue Sep 30, 2014 · 6 comments

Comments

@mohsen1
Copy link
Contributor

mohsen1 commented Sep 30, 2014

I want to use Schema as a bower module in Swagger Editor. It makes it easier to update the schema. Please publish schema.json as a bower and npm module independent from validator and make that a dependency of validator.

@webron
Copy link
Member

webron commented Sep 30, 2014

Are you talking about the json schema for 2.0?

@mohsen1
Copy link
Contributor Author

mohsen1 commented Sep 30, 2014

@webron let's talk about it here
https://github.com/wordnik/swagger-schema/issues/1

@RobDolinMS
Copy link
Contributor

@mohsen1 It looks like this hasn't been touched since 2014. Can it be closed?

@whitlockjc
Copy link
Member

whitlockjc commented Apr 26, 2017

I think it's a great idea honestly, to support Bower/NPM builds of the official schema(s). There use to be a module like this but I can't seem to find it.

@MikeRalphson
Copy link
Member

@whitlockjc there is this outdated package but it suffers from the limitation that it is not possible to have a dependency on more than one version of the package, i.e. for the v1.2 and v2.0 schemas. Resulting in this workaround from @mohsen1 himself.

I would prefer one package containing all (soon to be three) schemas with its own semantic version number, or separate official packages for each swagger/OpenAPI version. It would be ideal if schema changes automatically got published to npm as part of a successful travis build.

@handrews
Copy link
Contributor

This is asking for a subset of #2400, which has a detailed checklist and a linked PR. So let's just track it there - no need for two open issues.

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

6 participants