-
Notifications
You must be signed in to change notification settings - Fork 31
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
create test messages #13
Comments
example messages could be nested as part of "exampleUrlSchema" (inside each path's response or in components section) file or in separate files. I suggest we create separate example files for each event and add them as external component references into schema. With that approach will keep original schema clear. |
Yes, I like this approach. It also allows other organizations to define alternative url approaches for different purposes but reuse the examples. The example files themselves will assist with understanding so should be linked or referenced from any documentation. |
should examples be isolated form core files into own sub-folder - "examples" inside "Release Candidate Messages"? For each event there probably should be own example file aka. "IseminationEventExamples.json", "DryOffEventExamples"? |
Discussed in https://github.com/adewg/ICAR/wiki/Technical-Minutes-2020-01-31 |
Merge from ADEWG/ICAR/Develop
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
dummy messages in github so they can be accessed
The text was updated successfully, but these errors were encountered: