-
Notifications
You must be signed in to change notification settings - Fork 39
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
Generate warnings related to pads with :auto
flow control
#900
base: master
Are you sure you want to change the base?
Conversation
:auto
flow control
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.
I'm not sure that warnings are the best way to inform a user about behaviour that may be completely desired. IMO warnings should indicate that even though something won't necessarily break, it's definitely wrong, which is not the case here. That said, I have no idea for a better way to solve this :P
env.module | ||
|> Module.get_attribute(:__membrane_element_type__, :bin) | ||
|> case do | ||
:bin -> Membrane.Bin |
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.
shouldn't this apply to elements only?
lib/membrane/endpoint.ex
Outdated
@@ -25,6 +25,9 @@ defmodule Membrane.Endpoint do | |||
|
|||
Options: | |||
- `:bring_pad?` - if true (default) requires and aliases `Membrane.Pad` | |||
- `:flow_control_related_warnings?` - if true (default) generates compile-time warnings \ |
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.
What about
- `:flow_control_related_warnings?` - if true (default) generates compile-time warnings \ | |
- `:flow_control_hints?` - if true (default) generates compile-time warnings \ |
Closes #868
Closes #869