-
Notifications
You must be signed in to change notification settings - Fork 0
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
Architecture #16
Comments
Can somebody verify which of the next branches are actually up-to-date with what is used in the core app?
Commits diff states it's the first one, but I would like somebody to verify that. |
@artem-zakharchenko @honzajavorek From what I see in branches and history of git:
I can verify that there's that version published to $ npm view [email protected] gitHead
dd4d441efa04d948ba2009a83f70910ba3871c51 That ^^^ is the same hash as the last commit in branch ─ v0.1.0
└ kubula/customize_headers_converter
└ kubula/customize_json_converter_html |
#17 ensures current |
Published the actually used package version to NPM. Version: |
This library should get rewritten from scratch.
0.2.0-unstable.1
used by apiary.io works, but isn't in git, we do not have it's CoffeeScript code anywhere, npm contains only compiled JS.Update: The
gavel2html
branch for0.2.0-unstable.1
, which is used by apiary.io, has been recovered from @kuba-kubula's backup disk. It is now pushed to GitHub underkubula/customize_json_converter_html
branch name.The text was updated successfully, but these errors were encountered: