-
Notifications
You must be signed in to change notification settings - Fork 65
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
introduce displayBlock and deprecate display. #1500
introduce displayBlock and deprecate display. #1500
Conversation
This is a block and not a display that we get!
Stef, please don't. This changes makes everything more dirty. |
I will revert this PR |
also, the idea is that you will set what is going to be display. We don't care the nature of the parameter :) |
Your API is not good. And display is an order and it conflicts with the display. |
And BTW I do not see any evidence about
We can always pass a valuable instead of a block so this is a non argument. |
With this kind of design it means that we have to constantly check the code to be able to pass an argument. It looks like glamour APIs. Always guessing. Now I do not care but I will not document this . |
You see this design
prevent you to have displayUnderline: true Now you force people to guess that this is a block and to always pass a block when true is just enough. |
So what is the argument of |
This is a block and not a display that we get!