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
Multiple elements in one process (#293) #355
Conversation
94e6811
to
bca1121
Compare
3c2d4bf
to
aa70341
Compare
e1166ce
to
75d4a6b
Compare
Co-authored-by: Mateusz Front <mateusz.front@swmansion.com>
afbea4f
to
8d80c2a
Compare
lib/membrane/filter_aggregator.ex
Outdated
|
||
{name, module} -> | ||
unless is_atom(module) and module.membrane_element?() do | ||
raise "#{inspect(module)} is not an element!" |
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.
Let's raise something more like https://github.com/membraneframework/membrane_core/blob/master/lib/membrane/core/parent/child_entry_parser.ex#L53
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.
Do you mean the message, exception type or both?
I've started to write it as a ParentError
but I realized it might not be the best idea to treat FilterAggregator
as a parent in that scenario. I've used ArgumentError
instead as it's passed via options and raise happens on handle_init
. Any thoughts on that?
Closes #293