-
Notifications
You must be signed in to change notification settings - Fork 69
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
Export ui.card_body()
#1128
Comments
If we're going in on card_body()... From Lines 26 to 28 in e43e859
Can we have Then we can hoist items of |
Note that |
Another example noted in #1255:
|
Another example. Because app_ui = ui.page_fillable(
ui.layout_columns(
ui.card(
ui.output_ui("test_output"),
ui.input_checkbox("hide_input", "Hide Input Below", True),
ui.output_ui("test_output2"),
ui.output_ui("test_output3"),
),
),
) You can get around this by wrapping the elements in a |
Without making
ui.card_body()
public, it's impossible for app authors to give classes or attributes to the card body element that wraps the card body contents.One way this plays out is in the differences between
layout_sidebar()
and a dynamically created sidebar layout. If you giveui.card()
aui.layout_sidebar()
it doesn't wrap the sidebar layout into.card-body
:but if you create the sidebar layout dynamically, you don't have access to the card body wrapper and have to live with the padding it adds to the card, unless you do something that feels very off-label to call
ui._card.card_body()
Importantly, the
class_
argument ofui.card()
goes to the outer container, as do any tag attribute dictionaries.The text was updated successfully, but these errors were encountered: