-
Notifications
You must be signed in to change notification settings - Fork 10
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
Audio descriptions + closed captions -> jq rules #590
base: main
Are you sure you want to change the base?
Conversation
Minimum allowed line rate is |
@@ -204,6 +209,12 @@ impl BrokerOutput { | |||
} | |||
None | |||
} | |||
pub fn is_success(&self) -> bool { | |||
self.data.error.is_none() |
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.
Is it better to validate the result
field here ?
self.data.error.is_none() | ||
} | ||
pub fn is_failure(&self) -> bool { | ||
!self.is_success() |
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.
Similar comment, if error
field has some value, then data contains error response.
} | ||
None => None, | ||
}; | ||
} else if raw_value.get("success").is_some() { |
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.
This needs to be re-checked for result
and error
use cases.
result
response struct is implementation defined and success
field is not part of standard JSON-RPC 2.0 response format.
What
What does this PR add or remove?
Why
Why are these changes needed?
How
How do these changes achieve the goal?
Test
How has this been tested? How can a reviewer test it?
Checklist