-
Notifications
You must be signed in to change notification settings - Fork 26
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 the data model reference to the latest iroha dev revision #485
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
98e21e0
to
9d7004f
Compare
9d7004f
to
752aaa0
Compare
Signed-off-by: Nikita Strygin <dcnick3@users.noreply.github.com>
…g paths Signed-off-by: Nikita Strygin <dcnick3@users.noreply.github.com>
752aaa0
to
48643e4
Compare
…4544 Signed-off-by: Nikita Strygin <dcnick3@users.noreply.github.com>
Signed-off-by: Nikita Strygin <dcnick3@users.noreply.github.com>
As CI was failing due to broken links to |
I think it's totally fine. Thank you for updating schema generation too! |
This PR does three things:
While the inclusion of toml templates in place of old json files makes the config documentation "wrong", this allows writing new documentation with references to a more up-to-date
schema.json
.In the end I think the #397 will in the end remove the toml templates altogether, I consider this just a way to unblock my updates to the torii reference for hyperledger-iroha/iroha#4544
@0x009922 Do you think it's a good approach? Or should we try somehow to keep the old
json
's in place while the new config reference is not yet complete?