How to render conditional table rows ?

[martin-g]

Description

I need to render some table rows only when a specific Quarto profile is activated.

Here is a simple reproducer:

|    Variable    |      Meaning     |
|----------------|------------------|
| var1  | some value 1 |
| var2  | some value 2 |
::: {.content-visible when-profile="dummy"}
| var3  | some value 3 |
| var4  | some value 4 |
:::

I render it with: quarto render --profile dummy tables.qmd --to pdf ; open tables.pdf

But the rendered table is broken because of the empty line due to ::: {.content-visible when-profile="dummy"}:

What is the correct syntax ?

Thank you!

[mcanouil]

You can't make half tables and never will be able to do so.

Either generate the table programmatically and use the fact that profiles are defined using environment variables or duplicate part of the table.

::: {.content-visible unless-profile="dummy"}
|    Variable    |      Meaning     |
|----------------|------------------|
| var1  | some value 1 |
| var2  | some value 2 |
:::

::: {.content-visible when-profile="dummy"}
|    Variable    |      Meaning     |
|----------------|------------------|
| var1  | some value 1 |
| var2  | some value 2 |
| var3  | some value 3 |
| var4  | some value 4 |
:::

[martin-g]

Thanks for the quick answer, @mcanouil !
Could you please point me to an example of a programmatically generated table/content ?

[mcanouil]

I am not sure to understand.
it's just regular computation with whatever language you want to use.
There is a whole set of guides regarding computations, https://quarto.org/docs/guide/.
And regarding QUARTO_PROFILE, it is in the documentation you likely have read since you are using profiles, see https://quarto.org/docs/projects/profiles.html#activating-profiles.

```r
df <- data.frame(
  Variable = c("var1", "var2", "var3", "var4"),
  Meaning = c("some value 1", "some value 2", "some value 3", "some value 4")
)

if (Sys.getenv("QUARTO_PROFILE") %in% "dummy") {
  knitr::kable(df)
} else {
  knitr::kable(df[1:2, ])
}
```

[martin-g]

Thank you!

Actually, I am not using any languages (yet)!
I am working on a proof of concept for reworking OpenHPC's LaTeX based documentation to something more friendlier (like Markdown) that supports localization (I use Quarto's profiles for this).

[mcanouil]

I see, then it might be better to not use computation, as you will need to deal with dependencies (R or Python).

[jimjam-slam]

Since .content-visible uses the Pandoc div syntax, there's a good chance it can't be spliced into the middle of a table (that's me speculating!)

But if you don't want to deal with computational dependencies, you could put two versions of the whole table in .content-visible, the downside being some duplication :)

[mcanouil]

That's #7795 (comment) 😉