Trevor Lohrbeer

Possibly some additional information... I was experiencing the same behavior on 10.4.0 trying to test an emulated Firebase Auth flow. It turns out it was fixed by ensuring the redirect...

It would be nice to combine escaping HTML elements with a whitelist of HTML elements that are allowed to be parsed; anything else would be escaped. This would provide additional...

Another feature might be a sanitization function that can be run before the attributes are passed to the parsed element. While you can always provide custom components for everything, one...

Experiencing the same issue.

A workaround until this is supported natively is to use a JavaScript configuration file and build the scenarios dynamically. For example, create a `backstop.config.js` file similar to: ``` const defaultScenario...

Just ran into this issue too trying to make sure Corepack didn't alter the configuration on my system. Simple test case: ``` yarn --version # returns version corepack enable yarn...

> Generally, I feel like it's not a huge deal if `corepack enable/disable` are "destructive" operations. I'm more interested by the reasons why you'd call `disable`? In general, when trying...

Also, one of the reasons I looked into this is that the script in question had this line: ``` corepack prepare [email protected] --activate ``` Whoever wrote the script either didn't...

For those who want a safe way to enable/disable corepack, I wrote this bash script. With this script, `corepack-safe enable` will backup the existing environment before enabling `corepack` and `corepack-safe...

Checking in on this status as well. Any updates?