-
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
Feat/13 add json schema #16
Conversation
Docker image from this PR (f0f153b) created
|
Note that as of acf0d8e, this is installing the GitHub version of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
honestly, I'm totally lost with all this stuff, so just rubber stamping
Merging to unblock development, but opening an issue to improve documentation so that we're all comfortable with what's happening here |
Along with portfolios (in a standardized `csv` format), the parser exports a metadata file about the parsed inputs, and the exported portfolio files. | ||
The file is in JSON format, and validates against a [JSON Schema in this repository](inst/extdata/schema/parsedPortfolio_0-1-0.json). | ||
|
||
The file is array of objects, with the highest level opbects in the array centered around the input files, with the exported files contained in an array with the `portfolio` key in each input file object. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo: "opbjects"
"package": "digest", | ||
"version": "0.6.33" | ||
}, | ||
// ... array elided |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what does "elided" mean?
Merged before I could comment, but some potential typos |
Adds a JSON schema, validation logic to processing files, and metadata export
Closes #13
Closes #14