I think we should consider changing the way we do headers in our message components. The reason for this is for the situations when we do not have a header inside the message. The way to remove the header is a bit complicated, add an empty data-header="" attribute. Even though that might be clear to some users of the framework, you still need to jack with the content inside the message to combat the margin-bottom that still renders from the :before message header.
I believe messages were a pretty early component. At this point, I think we should style the message and maybe just let users add whatever content they want. I think the initial idea of adding the Header dynamically was pretty cool but it has the potential to overcomplicate the code.
🔧 Enhancement Request
I think we should consider changing the way we do headers in our message components. The reason for this is for the situations when we do not have a header inside the message. The way to remove the header is a bit complicated, add an empty
data-header=""attribute. Even though that might be clear to some users of the framework, you still need to jack with the content inside the message to combat themargin-bottomthat still renders from the:beforemessage header.I believe messages were a pretty early component. At this point, I think we should style the message and maybe just let users add whatever content they want. I think the initial idea of adding the Header dynamically was pretty cool but it has the potential to overcomplicate the code.
Who is asking for the feature?
Ted
What business problem is this hoping to solve?
Cleaner, UserFriendly framework.
Estimates