Skip to content
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

The semantic.css is too complicated. #157

Open
galachad opened this issue Jan 29, 2020 · 0 comments
Open

The semantic.css is too complicated. #157

galachad opened this issue Jan 29, 2020 · 0 comments
Assignees

Comments

@galachad
Copy link
Contributor

Currently is not possible to create html report using rmarkdown with self.contain option. It it not possible for pandoc to process semantic.css In the current state. Currently, we are using remote CDN for hosting external js/css for html reports.

Example:

semantic_html_document <- function(extra_dependencies = NULL, ...) {
  shiny_local = getOption("shiny.semantic.local")
  options("shiny.semantic.local" = TRUE)

  extra_dependencies <-
    append(
      extra_dependencies,
      get_dependencies()
    )
  options("shiny.semantic.local" = shiny_local)

  rmarkdown::html_document(
    extra_dependencies = extra_dependencies,
    self_contained = TRUE,
    ...
  )
}

The goal of this issue is research pandoc to process semantic.css

@galachad galachad self-assigned this Jan 30, 2020
@dokato dokato changed the title The semantic.css is to complicated. The semantic.css is too complicated. Oct 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants