epoxy_style_format() should work more like cli's inline formatting. Instead of

{fmt(airbnb$hosts, "number")} hosts

the syntax would be

{number {airbnb$hosts}}

# or maybe with leading dot?
{.number {airbnb$hosts}}

# or using a shortcut
{# {airbnb$hosts}}

to allow htmltools::tags without having to wrap in format().

library(shiny)
library(epoxy)

ui <- fluidPage(
  epoxyHTML("test", "<p>{{image}}</p>")
)

server <- function(input, output, session) {
  output$test <- renderEpoxyHTML(
    image = format(tags$img(src = "http://placekitten.com/200/200"))
  )
}

shinyApp(ui, server)

I am trying to use glue chunk to write the results of a model which I put inside a tibble. I want to use epoxy_style collapse() along with this and the results are weird. Also, the superscript doesn't seem to work inside the glue chunk.

```{r models}
m1<-lm(mpg~1,data = mtcars)
m2<-lm(mpg~factor(cyl),data = mtcars)
mods<-list(m1=m1,m2=m2)
results<-tibble(modnum=c("mod1","mod2"),models=mods)
results <-results %>% mutate(
        diag=map(models,glance)
) %>% unnest(diag) %>% slice(1:2)
```
```{glue modelres, eval=FALSE,.transformer=epoxy_style_collapse()}
{modnum} has an R^2 of {r.squared&}
```
```{glue ref.label="modelres",data=results}
```

I want results like this
mod1 has an R^2 of 0 and mod2 has an R^2 of 0.7333.

Since it could now be epoxyHTML (or renamed version, see #52) or epoxy_output_mustache.

The default branch of this repository is being moved from master to main. This issue will be closed when the default branch has been changed.

For help and guidance with updating the default branch of your local or forked copy of this repo, please see Renaming the default branch.

Search for files that may potentially reference master.

^{ID: 91e77a361e4e}

.dec is too ambiguous. I used it to be symmetric with .inc but I think .incr and .decr would be better. I'd prefer to use .desc but I don't think .asc is clear enough.

epoxy_mustache() that corresponds to ui_epoxy_mustache()? It would have slightly better semantics than whisker.render():

• Takes ... and does the same thing as epoxy() re named/unnamed arguments.
• Better aligns with Shiny's idea of truthiness, e.g. "" and NA are missing rather than counting as being included.
• Might have to apply the same truthiness filter to render_epoxy()? Or opt-in and enabled for ui_epoxy_mustache() by default.

Might also need to reconvince myself that c("inline", "html") is the right order.

epoxy seems to run into an error after updating R. It was working fine previously. I have tried after knitting too..

Here is the session info

R version 4.1.0 (2021-05-18)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build 19042)

Matrix products: default

locale:
[1] LC_COLLATE=English_India.1252 LC_CTYPE=English_India.1252
[3] LC_MONETARY=English_India.1252 LC_NUMERIC=C
[5] LC_TIME=English_India.1252

attached base packages:
character(0)

other attached packages:
[1] epoxy_0.0.2.9000

loaded via a namespace (and not attached):
[1] Rcpp_1.0.6 lubridate_1.7.10 tidyr_1.1.3 prettyunits_1.1.1
[5] ps_1.6.0 assertthat_0.2.1 rprojroot_2.0.2 digest_0.6.27
[9] utf8_1.2.1 R6_2.5.0 cellranger_1.1.0 backports_1.2.1
[13] reprex_2.0.0 evaluate_0.14 httr_1.4.2 ggplot2_3.3.5
[17] pillar_1.6.1 utils_4.1.0 rlang_0.4.11 curl_4.3.2
[21] readxl_1.3.1 rstudioapi_0.13 callr_3.7.0 rmarkdown_2.9
[25] readr_1.4.0 stringr_1.4.0 munsell_0.5.0 broom_0.7.8
[29] compiler_4.1.0 modelr_0.1.8 xfun_0.24 pkgconfig_2.0.3
[33] stats_4.1.0 pkgbuild_1.2.0 htmltools_0.5.1.1 tidyselect_1.1.1
[37] tibble_3.1.2 bookdown_0.22 grDevices_4.1.0 fansi_0.5.0
[41] crayon_1.4.1 dplyr_1.0.7 dbplyr_2.1.1 withr_2.4.2
[45] grid_4.1.0 jsonlite_1.7.2 gtable_0.3.0 lifecycle_1.0.0
[49] DBI_1.1.1 magrittr_2.0.1 datasets_4.1.0 scales_1.1.1
[53] zip_2.2.0 cli_2.5.0 stringi_1.6.2 fs_1.5.0
[57] remotes_2.4.0 tidyverse_1.3.1 xml2_1.3.2 ellipsis_0.3.2
[61] graphics_4.1.0 generics_0.1.0 vctrs_0.3.8 openxlsx_4.2.4
[65] base_4.1.0 tools_4.1.0 forcats_0.5.1 glue_1.4.2
[69] purrr_0.3.4 hms_1.1.0 processx_3.5.2 yaml_2.2.1
[73] colorspace_2.0-2 rvest_1.0.0 knitr_1.33 haven_2.4.1
[77] methods_4.1.0

... I noticed that your app is hosted on shinyapp.io. I am using a similar approach in our shiny app. This works absolutely fine on local.

But as soon as I deploy it to shinyapps.io I see it like this

Originally posted by @senthilthyagarajan in #6 (comment)

Currently you'd have to do something like this

epoxy_transform_set(
  epoxy_transform_inline(
    my_new_def = function(x) { ... }
  )
)

This would also unset previously established defaults, etc.

It'd be helpful to be able to directly add or update an inline transformer with a direct setter. Maybe:

1. epoxy_transform_inline_set() (too long)
2. epoxy_inline_set() (breaks pattern)
3. epoy_transform_set(.my_new_def = ) could special case arguments that start with .

Given the template ci:

    ```{glue ci, .open="(|", .close="|)", eval=FALSE}
    (|1+1|)
    ```

Having the following chunk pointing to the template is not enough:

    ```{glue n, ref.label="ci", data=dat}
    ```

It requires more parameters to work:

    ```{glue n, ref.label="ci", .open="(|", .close="|)", data=dat}
    ```

Might want to mention that or fix that. It appears that this will apply to all other parameters used in the template.

After #51 it's not just for epoxyHTML(), so epoxy_render() might be a better name, also following epoxy_{output,render} naming for Shiny functions.

https://and.rossellhayes.com/

Make sure they better sell inline formatters and the core usage of epoxy, since that has changed epoxy considerably.

use_epoxy_knitr_engines() should let the user set default values for things like .style.

Is there a way to include an R (or any other) chunk in the Glue chunk? I have a class assignment that wants us to answer questions with different values. In that, I need to include R code like this:

  ```{glue, .open="{{", .close="}}"}
  $$\alpha={{alpha}}$$
  $$\frac\alpha2={{alpha/2}}$$
  \```{r}
  z=qnorm(alpha/2, lower.tail = FALSE)
  z
  \```
  $$z_{\frac\alpha2}\approx {{z}}$$
  #Unable to include ending of block

Now I could just split the block up, but then it won't work as a template. Is the only way around it to format it by hand as a block? I would love this feature!

Use different wrapping strings for markdown, html and latex, e.g. epoxy_style_bold():

With RStudio 1.4 they introduced Visual Editor that allows LaTeX equations to be previewed, even if Visual Editor is off. However, it breaks when the equation is written in code blocks, is there a way to fix this? I don't know if this is even possible without modifying RStudio's code, so it might be a deep issue.

From this:

To something like this?

If you add back the ticks, the equation box stays there, but it will not update. It would be great if this was fixed, even without replacement of the variables is fine by me as it is like code. ({and } may mess up the LaTeX, so I used (| and |) so it would not mess it up.

A transformer wrapping scales functions.

I think the syntax might be something like

glue(
  "{s(sales_pct, '%')} of sales generated {s(revenue, '$')} in revenue.",
  sales_pct = 0.8,
  revenue = 125000,
  .transformer = epoxy_style_scales()
)

#> 80% of sales generated $125,000 in revenue

The central idea is that epoxy_style_scales() would make available a function s() with two arguments that is basically a switch around the scales::label_*() functions:

• % for label_percent()
• $ for label_dollar()
• si for label_scientific()
• p for label_pvalue()
• o for label_ordinal()
• b for label_bytes()
• d, ds, dt for _date, _date_short, _time
• etc...

maybe using partial matching so p --> pvalue.

Since the label function, e.g. label_percent(), take arguments and return a function that applies the formatting, epoxy_style_scales() would have an argument for each of the labellers and would accept a list of argument values for each.

Is there a way to add comments to glue chunks as we do in R?

# This is a comment in R

    ```{glue}
    # Comment in glue?
    ```

I remember having reasons why I switched away from this – likely due to an interaction with the inline transformer – but this doesn't feel right:

library(epoxy)
epoxy_html("<ul>{{li letters[1:3]}}<ul>")

<ul><li>a</li><ul>
<ul><li>b</li><ul>
<ul><li>c</li><ul>

The epoxy_style_format() inline formatter was an interesting idea, but ultimately I don't think it's as ergonomic as the inline foramtters. I'd rather remove it than publish epoxy on CRAN and have to support it or remove it soon thereafter.

Follow up from #51, I'd like to use epoxy_output as a prefix for epoxy-driven Shiny outputs.

Options:

• epoxy_output_html()
• epoxy_output()
• other (suggestions?)

Simple example using apreshill's bakeoff set:

```{r setup, include= FALSE}
library(bakeoff)
library(epoxy)
```

```{glue}
There are {nrow(bakeoff::series)} series of *The Great British Bake-Off* (or, **GBBO**).
```

The nrow correctly calculates, but the asterisks do not render italics or bold but just remain text, both inline in the code editor and in the Preview screen. I'm using the latest RStudio 4.1.0, glue 1.4.2, and epoxy 0.0.2.9000 on Mac OS.

This might be a useful example to include somewhere in the docs.

my_num <- 1234567890

epoxy(
  "* orig:  {my_num} or {my_num}\n",
  "* trunc: {.trunc_6 my_num}     or {.trunc_8 my_num}\n",
  "* head:  {.head_6 my_num}     or {.head_8 my_num}",
  .style = epoxy_style_inline(
    trunc_6 = \(x) glue::glue_collapse(x, width = 6),
    trunc_8 = \(x) glue::glue_collapse(x, width = 8),
    head_6 = \(x) substring(x, 1, min(nchar(x), 6)),
    head_8 = \(x) substring(x, 1, min(nchar(x), 8))
  )
)
#> * orig:  1234567890 or 1234567890
#> * trunc: 123...     or 12345...
#> * head:  123456     or 12345678

Prepare for release:

• git pull
• Check current CRAN check results
• Polish NEWS
• urlchecker::url_check()
• devtools::build_readme()
• devtools::check(remote = TRUE, manual = TRUE)
• devtools::check_win_devel()
• revdepcheck::revdep_check(num_workers = 4)
• Update cran-comments.md
• git push

Submit to CRAN:

• usethis::use_version('patch')
• devtools::submit_cran()
• Approve email

Wait for CRAN...

• Accepted 🎉
• usethis::use_github_release()
• usethis::use_dev_version(push = TRUE)

Great package, just scratched my exact itch. I like the usage style (as a Rmd dialect), very clean.

When trying to use epoxy, if knitr and/or rmarkdown libraries are not pre-loaded, you get the following error:

In get_engine(options$engine) :   
Unknown language engine 'glue' (must be registered via knit_engines$set())

Simple enough fix, but posting here for google-able posterity

Since we have a whisker engine, it might make sense to provide a ui_epoxy_whisker() alias for ui_epoxy_mustache().

They have different names at the moment because one uses the whisker package (which provides an R-based implementation of the mustache syntax) and the other uses mustache.js.

Use .comment = character() to enable # in pug-like syntax

See tidyverse/glue#193

I was wondering how can we use both (epoxy_style_collapse() and epoxy_style_bold() in the chunk.

i tried something like this

 "The mean of {st1$Variable} is {round(st1$Mean,3)&}"

but this throws an error

I called it the whisker engine because that's the R package name. And then I made ui_epoxy_mustache() because that's the javascript library name. But I gave an alias ui_epoxy_whisker() on the shiny side but not the knitr side. idk...

Pairs with #91

• bold, strong
• italic, emph
• code

The app below will fail unless a non-function text exists in the calling environment or if text = "something" is provided in epoxyHTML().

library(shiny)

# text <- "placeholder"

ui <- fluidPage(
  textInput("text", "Text"),
  epoxy::epoxyHTML("test", "{{text}}")
)

server <- function(input, output, session) {
  output$test <- epoxy::renderEpoxyHTML(text = input$text)
}

shinyApp(ui, server)

This is because graphics::text() is a function and found in the global environment, and glue::glue_data() later tries to call as.character() on the function, which fails.

I think the following should be the only way to set individual placeholder values.

ui <- fluidPage(
  textInput("text", "Text"),
  epoxy::epoxyHTML("test", "{{text}}", text = "placeholder")
)

I used .style and epoxy_style() because it felt a little more user friendly than transformer. But it has always felt a little awkward when writing the documentation: which thing am I talking about exactly? In which case transformer is the precise term. Also style gets confused with CSS styles or is otherwise a little too ambiguous.

I don't really want to change everything and my feeling is most people will use the currently named epoxy_style_inline() just by default. But I also don't want to be stuck with a naming convention that I'm not happy with.

I'm considering replacing style with transform or transformer everywhere:

• epoxy_transform()
• epoxy_transform_inline()
• epoxy_transform("bold", "collapse")

Yes, probably, especially with #89. Then you

• use the format with {.dollar expr}
• define the function with epoxy_transform_inline(.dollar = \(x) ...)
• or you update it with epoxy_transform_set(.dollar = \(x) ...)

Currently the non-dot argument name style of epoxy_transform_inline() would stand out

• Rename epoxy_style_default() -> epoxy_style_set()
• Add companion epoxy_style_get()

Currently substitution happens within an element, but it would be great to be able to substitute within an attribute.

expoxyHTML(
  a(href = "{{ url }}", "go to the link")
)

These have been around for a little while and I have a small amount of evidence that they've been used. I think the inline formatting is much cleaner and easier to understand.

Awsome work as usual!

Any plans making epoxy compatible with quarto files?

Since glue now loads it's own glue chunk engine.

Currently, epoxy_style_html() supports id and class attributes, but we could support additional attributes with something like this:

{{ a(href="https://example.com") link_text }}

In the long run, it'd be nice to be able to nest replacements, e.g.

{{ a(href="{{ link_url }}") link_text }}

or

{{ a href=link_url link_text }}

or maybe

{{ a c(href = link_url, link_text) }}

TODO:

• #73
• #74
• #86
• #85
• #88
• tabs not spaces
• #90
• #89
• #67
• Add get help on Discussions link to pkgdown site
• Add CoC?

Prepare for release:

• git pull
• Check current CRAN check results
• Check if any deprecation processes should be advanced, as described in Gradual deprecation
• Polish NEWS
• devtools::build_readme()
• urlchecker::url_check()
• devtools::check(remote = TRUE, manual = TRUE)
• devtools::check_win_devel()
• rhub::check_for_cran()
• revdepcheck::revdep_check(num_workers = 4)
• Update cran-comments.md
• git push
• Draft blog post

Submit to CRAN:

• usethis::use_version('minor')
• devtools::submit_cran()
• Approve email

Wait for CRAN...

• Accepted 🎉
• git push
• usethis::use_github_release()
• usethis::use_dev_version()
• git push
• Finish blog post
• Tweet
• Add link to blog post in pkgdown news menu