-
Notifications
You must be signed in to change notification settings - Fork 19
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
JSON validation schema #156
Comments
After getting 10M samples and validate them, this is a working proposal:
But, is it possible to narrow the schema for every different type: Crash:
Deprecation:
Intervention:
Network Error:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
Receiving the json reports from anywhere force to implement some filtering capabilities before store their content into the backend.
It would be helpful to have a JSON Schema with the predefined fields that are expected in the request.
Maybe this task is something that the parse consumers are forced to perform, but nowadays, each in their own personalized way.
Thanks,
The text was updated successfully, but these errors were encountered: