Gordon Leigh

@mazzy89 the 1password CLI deals with authentication. It supports [Biometric Unlock](https://developer.1password.com/docs/cli/get-started#sign-in) just like the browser extensions.

I turned off biometric support in the 1password preferences and as expected it needs a manual login instead. Here is what the 1password docs say on the matter: ``` AUTOMATIC...

@mtibeen I had also intended to also raise a PR for such a prompt, though I also agree with @hndrewaall. I actually started work on this already but I didn't...

Cool, thank you for sharing your subjective opinion with me. I need it because VS code auto-import messes up and imports stuff from deep inside packages sometimes, especially in monorepos,...

Opinions are subjective by definition. You don't define "deep importable" here, but if you're suggesting that a package consumer should expect to be able to import any file they please...

Is there any progress on this? As far as I understand, custom resource providers that access AWS services constitute a security hole, because they can make API calls that the...

I think this is a case of implementing in a similar fashion to AND ([source](https://github.com/vulcand/route/blob/20d2530fb5fba644d31762ad8f0581643ee75368/matcher.go#L57-L105)) and then wiring up in the [parse function](https://github.com/vulcand/route/blob/61904570391bdf22252f8e376b49a57593d9124c/parse.go#L31)

Thanks for the report. Can you show me a minimal code example that produces this error?

This is fixed in version 0.11.1 now available on npm.

Sorry for the delay. Thanks for your support. Not sure what you are referring to when you say the input is different from the native driver.