Skip to content

Request: make activate_js optional within bundle_resourcesΒ #1194

@LDSamson

Description

@LDSamson

Related to #503.

The use of activate_js is hard coded here:

golem::activate_js()

This will inject javascript from the golem-js.js file in the header with multiple custom message handlers:

golem/R/js.R

Line 43 in 6291796

system.file("utils/golem-js.js", package = "golem")

While you care considering deprecating the functions, according to #503, would you in the meantime consider making it possible to disable adding these custom message handlers within the function bundle_resources?

Our reason for getting rid of these functions are: we are currently not using them, and it provides an extra hurdle to create a strict and secure content-security-policy that we can use with our production-ready applications.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions