Selectr | A lightweight , vanilla javascript select box replacement

Errors like this in Shiny apps are almost always a result of missing packages, which the logs confirm.

Turns out in this case I think the missing package is kernlab, which I only found by reading the documentation given here: https://topepo.github.io/caret/train-models-by-tag.html#Support_Vector_Machines. It's a suggested package, not imported, so the command suggested in the comments by heds1 would sort this out.

I suggest you ditch IE support and get rid of -ms-grid-columns. grid-template-columns have broad browser compatibility by now and works for Edge.

That said, it seems like the value (1fr) should be without the parens. As far as I know there isn't any grid css that uses parenthesis, even though they are absolutely allowed in plain css, for example in var() and calc().

Here is if the targeted element is one there is no need of calling querySelectorAll just use querySelector the following is an example

I think this is ultimately a small bug in renv. Here's my guess at what's happening:

1. While this project has been initialized as an renv project, it does not have a lockfile for some reason. (Perhaps renv::activate() was called to initialize renv without explicitly creating a lockfile?)

2. The project has an renv autoloader; this is from a script at renv/activate.R. That script is configured to load renv 0.11.0.

3. When the project is loaded, renv finds that renv 0.12.0 is installed in the project library, not the expected version 0.11.0. This causes the warning to be emitted. (Perhaps renv was updated in that project previously?)

So, ultimately, the warning is misleading here -- the request for renv 0.11.0 comes directly from the autoloader, not from the lockfile (which does not exist). As for why the lockfile does not exist, I'm not sure -- but it most likely implies the project was initialized via renv::activate(), and not by renv::init().

All that said -- you can safely re-generate the lockfile via renv::snapshot().

you can't use same ID for pointing multiple elements in DOM, instead use CLASS.

so change your click event binding to a class instead of ID

Example

The error here occurs because on step_string2factor() during tuning, the recipe starts trying to handle variables that don't have any roles, like species and owner.

Try setting the role for all of your nominal variables before picking out the outcomes and predictors.

One way to add them is this:

In your model:

If you want to do it "properly", then you need to wrap all non-deterministic (non-pure) function calls in IO or IOEither (depending on whether they can or cannot fail).

So first let's define which function calls are "pure" and which are not. The easiest I find to think of it is like so - if function ALWAYS gives the same output for the same input and doesn't cause any observable side-effects, then it's pure.

"Same output" doesn't mean referential equality, it means structural/behaviour equality. So if your function returns another function, this returned function might not be the same function object, but it must behave the same (for the original function to be considered pure).

So in these terms, the following is true:

• cherio.load is pure
• $ is pure
• .get is not pure
• .find is not pure
• .attr is not pure
• .map is pure
• .filter is pure

Now let's create wrappers for all non-pure function calls: