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
Reference data set and generator #63
Reference data set and generator #63
Conversation
Added obsolete generator script (to be updated) along with dummy events file.
The validation script will no longer simply loop over schemas and attempt to apply to matching example files. Instead it reads all schemas, then reads all examples from all files, including lists of events (as found in examples/flows), then attempts to validate them all. The script also reports warnings for unchecked examples (due to missing schemas). The reason for implementing this change now is to be able to supportdevelopment development of large reference data sets.
41f2dc4
to
a52b66c
Compare
Hi Daniel , Maybe all that is needed to resolve the conflict is to clarify how to read the link flows with respect to time. |
plus it makes it hard to scale the link flow... |
Point taken. You should post it as an issue, though. |
Added a reference data set, consisting of events representing 5000 semi-random iterations of a hypothetical pipeline. Documentation and generator script included. This addresses issue #32.
Also updated the validation script to no longer simply loop over schemas and attempt to apply to matching example files. Instead it reads all schemas, then reads all examples from all files, including lists of events (as found in examples/flows), then attempts to validate them all. The script also reports warnings for unchecked examples (due to missing schemas). The reason for implementing this change now is to be able to supportdevelopment development of large reference data sets.