WTF, why do I need to clear the cache to see new integrations? By the way, using an incognito window works, but this is totally wrong (and it's probably a HASSIO fault)

Is your feature request related to a problem? Please describe. Storyshots-puppeteer is amazing in the sense that I get free test for almost all my components, that is awesome. However, sometimes I add artificial options to some of my components so I can test them properly. Forcing states like :hover or opening modals that are not meant to be controlled can be tricky.

Describe the solution you'd like I would love to be able to define a function per story so I can trigger some states before the snapshot is taken, so I don't need to add unneeded features to my components.

Describe alternatives you've considered Right now, the only option I see fit is to define my own API using the current beforeSnapshot global function

Are you able to assist bring the feature to reality? I can assist, but don't have time to code a solution

Just hit this issue, and I want to say that, they way I explore cmd usually is

command sub-command -h

So just displaying a bunch of options there without any explanation does not help much. I think adding a short explanation for each option will help many users. Thanks

Bumps lodash from 4.17.15 to 4.17.19. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lodash/lodash/releases">lodash's releases</a>.</em></p> <blockquote> <h2>4.17.16</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li><a href="https://github.com/lodash/lodash/commit/1144918f3578a84fcc4986da9b806e63a6175cbb"><code>1144918</code></a> Rebuild lodash and docs</li> <li><a href="https://github.com/lodash/lodash/commit/3a3b0fd339c2109563f7e8167dc95265ed82ef3e"><code>3a3b0fd</code></a> Bump to v4.17.16</li> <li><a href="https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12"><code>c84fe82</code></a> fix(zipObjectDeep): prototype pollution (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4759">#4759</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/e7b28ea6cb17b4ca021e7c9d66218c8c89782f32"><code>e7b28ea</code></a> Sanitize sourceURL so it cannot affect evaled code (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4518">#4518</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/0cec225778d4ac26c2bac95031ecc92a94f08bbb"><code>0cec225</code></a> Fix lodash.isEqual for circular references (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4320">#4320</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4515">#4515</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/94c3a8133cb4fcdb50db72b4fd14dd884b195cd5"><code>94c3a81</code></a> Document matches* shorthands for over* methods (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4510">#4510</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4514">#4514</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.19">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~mathias">mathias</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Now that I re-read the title this may not be my problem. I am not referencing the stories before they are defined, so it must be some other kind of bug

I'm also seeing this warning on storybook version 5

This is my story:

//@flow
import React from 'react'
import LinkTo from '@storybook/addon-links/react'
import UserBadge from '../UserBadge'

import Sidebar, { SidebarItem, SidebarMenu, SubmenuItem } from './'

export default {
  title: 'Sidebar',
  component: Sidebar,
  parameters: {
    options: { showPanel: false },
    info: {
      inline: true,
      header: false,
      styles: {
        infoBody: {
          height: '100vh',
          overflow: 'scroll',
          paddingRight: 0,
          position: 'absolute',
          left: '240px',
          top: 0,
          right: '10px',
        },
      },
    },
  },
}

/**
 * Use the default export to provide interactivity using knobs.
 * It will give a better overview of what the component is capable.
 */
export const Default = ({ active = 'payments' }: { active: string }) => {
  return (
    <Sidebar
      linkComponent={LinkTo}
      header={
        <UserBadge
          name="Cameron"
          surname="Diez"
          linkComponent={'a'}
          imgSrc="https://randomuser.me/api/portraits/women/49.jpg"
          options={[
            {
              icon: 'User',
              label: 'Account',
              href: '#',
            },
            {
              icon: 'CreditCard',
              label: 'Billing',
              href: '#',
            },
            {
              icon: 'InformationCircle',
              label: 'Support',
              href: '#',
            },
            {
              icon: 'Logout',
              label: 'Logout',
              href: '#',
              separator: true,
            },
          ]}
        ></UserBadge>
      }
    >
      <SidebarMenu>
        <SidebarItem
          icon="Calendar"
          story="Payroll Active"
          label="Payroll"
          active={active === 'payroll'}
        ></SidebarItem>
        <SidebarItem
          icon="Users"
          linkComponent={LinkTo}
          story="Users-Active"
          label="Employees"
          active={active === 'employees'}
        ></SidebarItem>
        <SidebarItem
          icon="CreditCard"
          linkComponent={LinkTo}
          story="Default"
          label="Payments"
          active={active === 'payments'}
        ></SidebarItem>
        <SidebarItem
          icon="ChartBar"
          linkComponent={LinkTo}
          story="Reports Active"
          label="Reports"
          active={active === 'reports'}
        ></SidebarItem>
        <SidebarItem
          icon="Library"
          label="Company"
          story="Company Active"
          linkComponent={LinkTo}
          active={active === 'company'}
        >
          <SubmenuItem active={active === 'general'} story="General Active">
            General
          </SubmenuItem>
          <SubmenuItem active={active === 'HMRC'} story="HMRC Active">
            HMRC
          </SubmenuItem>
          <SubmenuItem active={active === 'pension'} story="Pension Active">
            Pension
          </SubmenuItem>
          <SubmenuItem active={active === 'allowance'} story="Allowance Active">
            Allowance
          </SubmenuItem>
        </SidebarItem>
        <SidebarItem
          icon="Cog"
          story="Integrations Active"
          label="Integrations"
          linkComponent={LinkTo}
        ></SidebarItem>
      </SidebarMenu>
    </Sidebar>
  )
}
export const UsersActive = () => <Default active="employees" />

export const CompanyActive = () => <Default active="company" />
export const PayrollActive = () => <Default active="payroll" />
export const ReportsActive = () => <Default active="reports" />
export const GeneralActive = () => <Default active="general" />
export const IntegrationsActive = () => <Default active="HMRC" />
export const HMRCActive = () => <Default active="HMRC" />
export const PensionActive = () => <Default active="pension" />
export const AllowanceActive = () => <Default active="Allowance" />

What does people have against the mentioned plugins?

Is your feature request related to a problem? Please describe. Easy motion is awesome, but sometimes one character is not enough, using always both is too cumbersome, and even sometimes two is not enough.

Describe the solution you'd like In vim, easymotion has an incremental version that lets you type as many characters as you want to narrow down the list of options, then you just hit enter an navigate to the one that you want using the usual easymotion markers.

Describe alternatives you've considered There is the normal version of easy motion, but it is not as powerful

Additional context Hope this screencast clarifies things:

<iframe src='//gifs.com/embed/easy-motion-2xMBYA' frameborder='0' scrolling='no' width='656px' height='584px' style='-webkit-backface-visibility: hidden;-webkit-transform: scale(1);' ></iframe>

I'm pretty sure the problem is a combination of keybindings overrides and lack of docs (both, on this repo and on VSCodeVim one). Not sure if this plugin uses space as default to activate the which key, but VSpaceCode does. Given that there is no documentation about how to remap keys when you run a WhichKey command/option (I know there is now an issue for that) and that the only way according to VSCodeVim docs (https://github.com/VSCodeVim/Vim#vim-easymotion) to activate easymotion is by remapping keys (there is nothing like vim.easymotionForward) I'm pretty sure that is the root cause of this problem.

Bumps lodash from 4.17.10 to 4.17.20. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/ded9bc66583ed0b4e3b7dc906206d40757b4a90a"><code>ded9bc6</code></a> Bump to v4.17.20.</li> <li><a href="https://github.com/lodash/lodash/commit/63150ef7645ac07961b63a86490f419f356429aa"><code>63150ef</code></a> Documentation fixes.</li> <li><a href="https://github.com/lodash/lodash/commit/00f0f62a979d2f5fa0287c06eae70cf9a62d8794"><code>00f0f62</code></a> test.js: Remove trailing comma.</li> <li><a href="https://github.com/lodash/lodash/commit/846e434c7a5b5692c55ebf5715ed677b70a32389"><code>846e434</code></a> Temporarily use a custom fork of <code>lodash-cli</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/5d046f39cbd27f573914768e3b36eeefcc4f1229"><code>5d046f3</code></a> Re-enable Travis tests on <code>4.17</code> branch.</li> <li><a href="https://github.com/lodash/lodash/commit/aa816b36d402a1ad9385142ce7188f17dae514fd"><code>aa816b3</code></a> Remove <code>/npm-package</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.10...4.17.20">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~bnjmnt4n">bnjmnt4n</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps sshpk from 1.13.1 to 1.16.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/joyent/node-sshpk/releases">sshpk's releases</a>.</em></p> <blockquote> <h2>v1.16.1</h2> <ul> <li>Fixes for <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/60">#60</a> (correctly encoding certificates with expiry dates >=2050), <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/62">#62</a> (accepting PKCS#8 EC private keys with missing public key parts)</li> </ul> <h2>v1.16.0</h2> <ul> <li>Add support for SPKI fingerprints, PuTTY PPK format (public-key only for now), PKCS#8 PBKDF2 encrypted private keys</li> <li>Fix for <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/48">#48</a></li> </ul> <h2>v1.15.2</h2> <ul> <li>New API for accessing x509 extensions in certificates</li> <li>Fixes for <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/52">#52</a>, <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/50">#50</a></li> </ul> <h2>v1.14.1</h2> <ul> <li>Remove all remaining usage of jodid25519 (abandoned dep)</li> <li>Add support for DNSSEC key format</li> <li>Add support for Ed25519 keys in PEM format (according to draft-curdle-pkix)</li> <li>Fixes for X.509 encoding issues (asn.1 NULLs in RSA certs, cert string type mangling)</li> <li>Performance issues parsing long SSH public keys</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/joyent/node-sshpk/commit/1aece0d1df155e60e4cb0ae42cb3ed7aa043e174"><code>1aece0d</code></a> <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/60">joyent/node-sshpk#60</a> certs should generate GeneralizedTime values for dates >...</li> <li><a href="https://github.com/joyent/node-sshpk/commit/684dbe66d9615378bdb4d1ac1ede9f901591cb86"><code>684dbe6</code></a> <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/62">joyent/node-sshpk#62</a> handle pkcs8 ECDSA keys with missing public parts</li> <li><a href="https://github.com/joyent/node-sshpk/commit/574ff21e77117b478baf4664856bfc4b0aa41a12"><code>574ff21</code></a> <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/18">joyent/node-sshpk#18</a> support for PKCS8 encrypted private keys</li> <li><a href="https://github.com/joyent/node-sshpk/commit/f647cf22c3258ef514d2ba098a4a6aad3492f425"><code>f647cf2</code></a> <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/27">joyent/node-sshpk#27</a> Add support for PuTTY PPK format</li> <li><a href="https://github.com/joyent/node-sshpk/commit/44aec4ad8bcf7324009c92a52e4c81487cbc24b9"><code>44aec4a</code></a> <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/59">joyent/node-sshpk#59</a> want support for SPKI fingerprint format</li> <li><a href="https://github.com/joyent/node-sshpk/commit/385ff11efc4edd201c07f2ceee23746c13122f9c"><code>385ff11</code></a> <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/48">joyent/node-sshpk#48</a> wish: add support for x509 certificates in text form</li> <li><a href="https://github.com/joyent/node-sshpk/commit/c7a6c6833370f69322c47e73e9f4cfdedaf4e8f4"><code>c7a6c68</code></a> <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/58">joyent/node-sshpk#58</a> des-ede3-cbc encrypted keys broken</li> <li><a href="https://github.com/joyent/node-sshpk/commit/2ab4f2a018766559252f2c3426a3735f0860ac0d"><code>2ab4f2a</code></a> <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/56">joyent/node-sshpk#56</a> md5 fingerprints not quite right</li> <li><a href="https://github.com/joyent/node-sshpk/commit/026ef4764a55648dd15f45f7f14ff9da5d1fe2ad"><code>026ef47</code></a> <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/53">joyent/node-sshpk#53</a> stop using optional deps to fix webpack</li> <li><a href="https://github.com/joyent/node-sshpk/commit/53e23feff41226826b45293bc4a9fc45f2e44afe"><code>53e23fe</code></a> <a href="https://github-redirect.dependabot.com/joyent/node-sshpk/issues/50">joyent/node-sshpk#50</a> Support PKCS#5 AES-256-CBC encrypted private keys</li> <li>Additional commits viewable in <a href="https://github.com/joyent/node-sshpk/compare/v1.13.1...v1.16.1">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps mixin-deep from 1.3.1 to 1.3.2. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jonschlinkert/mixin-deep/commit/754f0c20e1bc13ea5a21a64fbc7d6ba5f7b359b9"><code>754f0c2</code></a> 1.3.2</li> <li><a href="https://github.com/jonschlinkert/mixin-deep/commit/90ee1fab375fccfd9b926df718243339b4976d50"><code>90ee1fa</code></a> ensure keys are valid when mixing in values</li> <li>See full diff in <a href="https://github.com/jonschlinkert/mixin-deep/compare/1.3.1...1.3.2">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~doowb">doowb</a>, a new releaser for mixin-deep since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps lodash.template from 4.4.0 to 4.5.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/ab73503859a2d2f7f603bc8a293ce93ecc071e83"><code>ab73503</code></a> Bump to v4.5.0.</li> <li><a href="https://github.com/lodash/lodash/commit/a4f7d4cc2a3b6d3a43f6c27beadbf90410eecdcd"><code>a4f7d4c</code></a> Rebuild lodash and docs.</li> <li><a href="https://github.com/lodash/lodash/commit/cca5ac60d61a2f786eeafadb674d6e12fc6179c8"><code>cca5ac6</code></a> Fix npm-test by removing the call to test-docs.</li> <li><a href="https://github.com/lodash/lodash/commit/9f7f9fc3c5f1a4db9a2134950872440c792ee8bb"><code>9f7f9fc</code></a> Adjust heading order. [ci skip]</li> <li><a href="https://github.com/lodash/lodash/commit/6e2fb92e9a2fd29ef630f71bd571afcdf0f2e206"><code>6e2fb92</code></a> Remove unused <code>baseArity</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/4f702e238183444ff392c3c7be5b48f1a7271519"><code>4f702e2</code></a> Specify utf8 encoding.</li> <li><a href="https://github.com/lodash/lodash/commit/b188f903ce41e624d6169f47a0c9e5091c178160"><code>b188f90</code></a> Add fp tests for iteratee shorthands.</li> <li><a href="https://github.com/lodash/lodash/commit/7b93dc9c3253c342a45881392d2308374a8909b3"><code>7b93dc9</code></a> Ensure clone methods clone expando properties of boolean, number, & string ob...</li> <li><a href="https://github.com/lodash/lodash/commit/664d66a89ec553438d5560239eba24d30867e580"><code>664d66a</code></a> Make string tests more consistent.</li> <li><a href="https://github.com/lodash/lodash/commit/d9dc0e6fd13c030029964b5ba468e0df3e2de3b2"><code>d9dc0e6</code></a> Add <code>_.invertBy</code> tests.</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.4.0...4.5.0">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps acorn from 6.3.0 to 6.4.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/acornjs/acorn/commit/9a2e9b6678e243d66846b91179d650d28453e70c"><code>9a2e9b6</code></a> Mark version 6.4.1</li> <li><a href="https://github.com/acornjs/acorn/commit/90a9548ea0ce351b54f956e2c4ed27cca9631284"><code>90a9548</code></a> More rigorously check surrogate pairs in regexp validator</li> <li><a href="https://github.com/acornjs/acorn/commit/df0cf1a3e2b1a51a26c14984dc0f5412b7151b10"><code>df0cf1a</code></a> Mark version 6.4.0</li> <li><a href="https://github.com/acornjs/acorn/commit/53034126864b492da4e278628bb972cb2a9313d4"><code>5303412</code></a> Also export Parser via Parser.acorn</li> <li><a href="https://github.com/acornjs/acorn/commit/efe273e70123449a458157dbf578afaf109a49ab"><code>efe273e</code></a> give token types and etc to plugins</li> <li>See full diff in <a href="https://github.com/acornjs/acorn/compare/6.3.0...6.4.1">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps lodash from 4.17.15 to 4.17.20. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/ded9bc66583ed0b4e3b7dc906206d40757b4a90a"><code>ded9bc6</code></a> Bump to v4.17.20.</li> <li><a href="https://github.com/lodash/lodash/commit/63150ef7645ac07961b63a86490f419f356429aa"><code>63150ef</code></a> Documentation fixes.</li> <li><a href="https://github.com/lodash/lodash/commit/00f0f62a979d2f5fa0287c06eae70cf9a62d8794"><code>00f0f62</code></a> test.js: Remove trailing comma.</li> <li><a href="https://github.com/lodash/lodash/commit/846e434c7a5b5692c55ebf5715ed677b70a32389"><code>846e434</code></a> Temporarily use a custom fork of <code>lodash-cli</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/5d046f39cbd27f573914768e3b36eeefcc4f1229"><code>5d046f3</code></a> Re-enable Travis tests on <code>4.17</code> branch.</li> <li><a href="https://github.com/lodash/lodash/commit/aa816b36d402a1ad9385142ce7188f17dae514fd"><code>aa816b3</code></a> Remove <code>/npm-package</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.20">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~bnjmnt4n">bnjmnt4n</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Ok, that command vim.remap and the args property is what I was missing. Is it documented anywhere?

By the way, a possible workaround is to hide the vspacecode bindinb behind a double leader key or a different leader key:

    {
      "before": ["<space>", "<space>"],
      "commands": ["vspacecode.space"]
    }

So, this plugin is supposed to ve a super-set of VSCodeVim keybindings, but I don't see a way to do things that were possible with the VSCodeVim. For example, imagine I want to insert a whiteline above the cursor:

    {
      "before": [" ", "k"],
      "after": ["O", "<Esc>"]
    },

How can I do that with this extension ?

@MarcoIeni the template is nice when you want to report a bug, but this is just a functionality that is not taken in account. I think the title and the description are descriptive enough. I'm having the same problem by the way.

Hello @xanmanning ,don't worry. I tried that option too, but then other permissions problems arised, so I decided to take the easy way.

I am also having a similar behavior

Hello, Thanks for this awesome project, I love the idea. I'm trying to render a smaller bersion of the board, like this board_A( 10, 15 ); but it has been rendering (I opened just that file on openscad) for more than an hour. How long is it expected torun?

Dam it! I can't believe it! I just finished at the exact moment I clicked the submit issue button, to the point that I thought "Uh, when did the submit button started to emit sounds" and it was openscad finishing the render!

Hello, Thanks for this awesome project, I love the idea. I'm trying to render a smaller bersion of the board, like this board_A( 10, 15 ); but it has been rendering (I opened just that file on openscad) for more than an hour. How long is it expected torun?

No worries @germ, and thank you very much

Hello @onedr0p ,what do you mean by not working? Not working at all or behaving incorrectly? Or do you refer to the tokens that I specifically mentioned? I have it mine running and the logs shows a normal operation, so unless it is not working but showing promising logs It is working for me

Hello, I am missing some config options for the cloudflare dyndns chart, specifically CF_APITOKEN. This is used to provide a more restricted token so the app has much more limited access. Because it is not documented, I decided to take a look at the chart code, but I was not able to find it. Where is it? And, will you consider adding this configuration options? Thanks and regards

I just used 10.0.0.0/8

$CIDR

What is the $CIDR var supposed to contain?

Hello, Thank you for this role.

I am folowing the most basic setup provided, and I am running into the following error:

Destination /usr/local/bin is not writable

The target is an ubuntu server:

Linux lab01 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

this is the specific playbook I'm using:

- name: Rancher nodes
  hosts: rancher
  become: yes
  roles:
    - { role: xanmanning.k3s, k3s_release_version: v1.16.15+k3s1 }

Not sure what I can do about it

Adding k3s_become_for_all: yes fixed my problem.

Hello, Thank you for this role.

I am folowing the most basic setup provided, and I am running into the following error:

Destination /usr/local/bin is not writable

The target is an ubuntu server:

Linux lab01 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

this is the specific playbook I'm using:

- name: Rancher nodes
  hosts: rancher
  become: yes
  roles:
    - { role: xanmanning.k3s, k3s_release_version: v1.16.15+k3s1 }

Not sure what I can do about it

@mokkabonna what about short circuit in case of one specific choice? How would you implement that?

Wow, I just tried to setup a CI workflow and I was going to open a new issue asking what to do about the interactive login step. So after setting up all the google project and that stuff this is indeed not supported. How long is this from being implemented? Is this considered or is it a won't do?

What is this missing for being merged?

What kind of change does this PR introduce?:

Did you add tests for your changes?:

Summary:

Does this PR introduce a breaking change?:

Other:

People expects modals to be closed by clicking outside of them. This will also allow to safely remove the footer for those that does not like it.

This will allow third party plugins and customization to add elements to the Basics table of the control panel. The lack of <tr> tags is intentional so each tiddler can decide if they want to add one or more than one row at a time. Table does not merge with the one above, which may be both a good and a bad thing, I want to open the discussion about it.

Tiddlers may look like this:

<tr>
<td><$link to="$:/config/NewJournal/Tags"><<lingo NewJournal/Tags/Prompt>></$link> </td><td><$edit-text tiddler="$:/config/NewJournal/Tags" default="" tag="input"/></td>
</tr>

Hello @ftchirou

This PR is not meant to be merged, but I think it is a good place to talk about some things that I think you can use on your examples. Also I want to talk about some decisions you made about how tokens are defined.

Highlights of this PR are:

• Two classes extending the base FSM class. One for strings and another one for numbers. I feel this helps to keep things cleaner and scoped as opposed to create a method inside the lexer that has the entire logic the number FSM needs
• The FSM class is able to accept the nextToken function (to the interface has not changed) but it is also able to use the nextToken of an extending class. This way you have the best of both worlds
• The FSM accepts the NoNextState identifier, there is no other way to know which state corresponds to the NoNext one
• I have implemented several of the CharUtils with concise regular expressions
• I dried the code with some functional programming techniques taking advantage of closures and partial application
• I have created a new class BiMap that is used for managing the different keywords (operators, keywords, delimiters...) This class has the ability to search both by value or by key, which is handy when you want to know when a token is of certain type.

You may notice that there are several tokens where I just use the same value both for the type and the value. This is because the hash-map of keyworks works this way, and it is one of the things I want to talk with you. I can't see the possible problems at this moment, but mapping the type name to the actual type value looks a bit redundant, specially when you look at the tokens, where the type is the same as the value {type:'+', value:'+'} . Probably reversing the idea has more sense, so the type will be extracted using the value as mapping mechanism. But I have no experience on this field, and I have no Idea how the next phases will be implemented, so maybe I'm making wrong assumptions here.

The code can be improved of course and make it more robust, but I think at it's current state is good enough to show some of ES6 best features.

Regards

@drashna I just made the mentioned cleanup. Can you take another look?

Hello, thank you very much for this awesome project,I started using combos recently and this is a game changer. The references to the stenography engine caught my attention, but I can’t find any docs related. From looking at the code I deduce the following:

• It shadows some QMK features, so maybe things like tap dance does not work.
• it has some keys that activate an special “enter a long chord here” mode that may not rely on timeouts
• for some reason the qmk keys are redefined with some stenography conventions like GA for KC_A, not sure why this is needed other than shorter definitions

I will be very grateful if some extra and accurate info is included to see if I want to use it on my keyboards (or at least on my gengi) Thanks and regards

Don't worry @pbiggar, I'm using reason standard for now. Since most of the docs seems to come from there it is probably a good substitute for many. I'll be looking for the release (with standard merged in)

So all the documentation that I have been reading for more than one hour is basically useless? I want to use the Map.String module and I'm getting an error telling me that such module does not exist, then I checked the mli files and indeed there is no definition for that.

This is on the usage page, first example:

open Tablecloth;
String.toList("Tablecloth")
->List.filterMap(~f=character => 
  Char.toCode(character)->Int.add(1)->Char.fromCode
)
->String.ofList

However, string ofList does not exist, the correct one is String.fromList (much more natural IMO)

I don't want to insist, but I think it's important to at least keep the issue open

Seems that you just declare stuff on the global scope : https://developers.google.com/apps-script/guides/v8-runtime/migration

I'll make some tests later to see if there is a window or global objects, they are using V8 after all

That is a tricky question, but my guess is that it should be global or maybe window

Hey, this is the heading of the bundled version of sanctuary:

(function(f) {

  'use strict';

  /* istanbul ignore else */
  if (typeof module === 'object' && typeof module.exports === 'object') {
    module.exports = f ();
  } else if (typeof define === 'function' && define.amd != null) {
    define ([], f);
  } else {
    self.sanctuaryShow = f ();
  }

} (function() {

That self on the last else is not defined anywhere, leading to an exception. Is this a bug? Is is happening to me because I have copied sanctuary bundle into an appscript project. Do I need to include anythig else?

@danielo515 I very rarely use surround, what sort of visual feedback are you expecting? The operator-in-progress cursor will be there in the next release - is there anything else?

Any command that requires you to look at the bottom bar has this feeling. Some commands appear centered on the bottom bar while others appear shifted to the right, and it takes a second or two to find it in the absolute mess the bottom bar is. It will be better to have a pop-up or some kind of inline visual feedback, but I'm not sure if vscode allows such thing

Thanks for your efforts @J-Fields ! they made my editor way more usable. There are still problems with perceived slowness because sometimes you don't see the result of your commands. Like when you want to surround something, you hit yst (for a tag) and nothing happens, then you type the surrounds and it works, but the feeling is that it is slow because you don't see any change on your screen (or, if there is any, it is too hard to spot)

Describe the bug (required) The ID that is provided to the filterFunctions is not a string. Looking at the examples (the only source where you can see what the filter functions get) it is used to access an object property like if it was an stirng, but in reality it is an array, so the lookup will always fail.

Provide an example via Codesandbox! (required) react-table codesandbox to reproduce the issue.

Steps To Reproduce (required)

1. Go to the sandbox
2. Change the profile progress
3. Check the console
4. See the logged ID as an array

Expected behavior (Recommended) I actually expect the examples and docs to be updated

Hello, if you follow the suggestion of this extension of disabling the javascript/typescript built in extension you loose some features that are not provided by this extension. One of them is the auto completion and auto-indentation of jsdoc blocks. In normal VSCode if you write /* you automatically get a jsdoc block that then it gets a leading * on every new row and it is automatically indented, this no longer works if you use this extension with built int js/ts extension disabled.