integrations / snappydoo

Turns Jest snapshots into Slack message builder screenshots

Turns Jest snapshots into Slack message builder screenshots.

snappydoo's Issues

Allow running specific snapshots

When someone else commits changes to snapshots, the only way to regenerate the screenshots is to run -a. It'd be nice if I could pass the name of the files.

Then I could have run this to regenerate snapshots that changed in the current branch:

$ snappydoo $(git diff --name-only master -- test/messages/__snapshots__)

Configure concurrent processed and limit with bottleneck

User should be able to specify the limit
Default should probably be 2 but will require more testing

{
  "snappydoo": {
    "in": "/some/path",
    "out": "/some/path",
    "limit": 4
  }
}

Strip out image metadata to make builds more deterministic

Given consistent input running snappydoo on the same machine will create the exact same output. Running it on a different machine, however, with the same input, leads to a different output. This is not good for our use case and pollutes the diff.

Need to explore options for how to strip out metadata.

Allow user to specify retry limit

In snappydoo config

package.json

{
  "snappydoo": {
    "in": "/some/path",
    "out": "/some/path",
    "retry": // number of times to retry if a message didn't load. Default: 1
  }
}

Newlines are removed from messages

Allow specifying excluded files by regular expression

In snappydoo config

{
  "snappydoo": {
    "exclude": [
      "SnapshotFileName", // exclude files with exactly this filename (when `test.js.snap` is appended)
      {
        type: "regex",
        expression: "(.*)" // exclude all files that match this expression
      }
    ]
  }
}

Load only files that have changed since last commit

Right now, generating the ~33 screenshots takes around 2 minutes. Only loading the files that have changed would be much more efficient

• console.log() how long it took to complete

updating npm packages in npm

@dennissivia , I updated packages and fixed dependabot alerts in this repo. But, I see that it is published from private account. Is there any way to publish this new patch ??.

Remove fs-path and upgrade some packages

The fs-path package has an unfixed security vulnerability https://www.npmjs.com/advisories/661

There are other alerts here https://github.com/integrations/snappydoo/network/alerts

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.