Request: mark NSE-friendly functions in documentation

[MichaelChirico]

I maintain some metaprogramming tools that need to be NSE-aware to avoid flagging code with spurious "undefined objects" warnings from codetools::checkUsage().

For tidyr and dplyr, I can search the documentation for certain links to get a good head start on which functions are NSE-friendly,

e.g. tidyr might use <tidy-select>:

https://github.com/tidyverse/tidyr/blob/0764e65fad777b71aa2a81ffd5447d04a61f8d5e/R/pivot-long.R#L17-L18

Would it make sense for {gt} to offer similar hints in the documentation about where NSE might show up in its calls?

[rich-iannone]

Makes perfect sense! I think it's a good idea and one we'll get to for the next release.

[rich-iannone]

We now have something akin to this for every exported function (check out https://gt.rstudio.com/reference/data_color.html for an example). Closing this now.