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

Update Swagger-Schema-Official on npm #335

Closed
JamesMessinger opened this issue Apr 20, 2015 · 8 comments · Fixed by #336
Closed

Update Swagger-Schema-Official on npm #335

JamesMessinger opened this issue Apr 20, 2015 · 8 comments · Fixed by #336

Comments

@JamesMessinger
Copy link
Contributor

The swagger-schema-official package on npm hasn't been updated in six months.

@mohsen1
Copy link
Contributor

mohsen1 commented Apr 20, 2015

It's updated.

@JamesMessinger
Copy link
Contributor Author

The new version on npm is exactly the same as the previous version. None of the new changes are there.

@JamesMessinger
Copy link
Contributor Author

Would it be possible to add a version number to the JSON Schema? That would make it much easier to track schema changes, especially if the version number of the JSON Schema was kept in sync with the version number on NPM.

@mohsen1
Copy link
Contributor

mohsen1 commented Apr 21, 2015

My bad, my git origin remote was pointed to my fork. [email protected] should have the latest

@JamesMessinger
Copy link
Contributor Author

Thanks @mohsen1! Looks good now.

@JamesMessinger
Copy link
Contributor Author

The swagger-schema-official package on npm has gotten outdated again. It's been about six months since it was last updated.

@mohsen1 - would you consider making me a contributor on the npm package? If so, I would gladly keep it updated, since I depend on it for Swagger Parser.

@mohsen1
Copy link
Contributor

mohsen1 commented Oct 2, 2015

@BigstickCarpet published [email protected]. I don't have access to give you owner permission. I'll try to keep this up to date.

@JamesMessinger
Copy link
Contributor Author

Thanks, @mohsen1! It works perfectly. Thanks for taking care of it so quickly!

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 a pull request may close this issue.

2 participants