-
Notifications
You must be signed in to change notification settings - Fork 7
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
Schema files are out of date #7
Comments
Needed for flowbased/flowtrace#16 |
Now we the prose in this project at https://github.com/flowbased/fbp-protocol/blob/master/spec/protocol.md and we generate docs from and autodeploy to: http://flowbased.github.io/fbp-protocol |
@jonnor, @ifitzpatrick and I can write a python script for this. I'm considering using jinja so that we can make a template .md file that loops over data pulled from the schema files. That will give us easy control over how the final doc is built. |
Cool. Yep, generating an .md for the things coming from schema (or a set of On 18 May 2016 at 22:55, Chad Dombrova [email protected] wrote:
Jon Nordby - www.jonnor.com |
Related to #17 |
Yep. Saw it and thanks for reviewing. Should be taken care of early next week. |
To close this ticket I think we just need the flowtrace stuff. @jonnor is that feature targeted for version 0.6 of the protocol? |
I think we should keep version bumps (like going to 0.6) to incompatible changes only. |
Sure, makes sense. |
flowtrace stuff now in schemas, https://github.com/flowbased/fbp-protocol/blob/master/schema/yaml/trace.yml |
To get out of this, we should make the schemas the canonical single-source-of-truth for all protocol description. Currently this information is in https://github.com/noflo/noflo.github.io/blob/master/documentation/_posts/2013-07-09-protocol.md
The human-readable documentation page should be generated from the JSON schemas
The text was updated successfully, but these errors were encountered: