Given the immense popularity of Docker and the need to harden it different per platform (see ideas below) - we'd like to start writing a Docker best practices section.

You're welcome to contribute ideas and write best practices - writing and brainstorming will people is an amazing way to deepen your Docker understanding.

At first, we want to collect ideas for best practices, solidify a list

Current behavior

Hello, I would simply like to request that the documentation for find() (https://enzymejs.github.io/enzyme/docs/api/ShallowWrapper/find.html) be updated to reflect its snapshot-nature. For example, in a situation where clicking a button updates state under the hood...

   // some set up code goes here. 

    const deleteButton = wrapper.find('[data-enzyme-id

The second example in section 1.1 says:

expect(result.approved).to.be.false;

It should be:

expect(result.approved).to.be.true;

(I'm guessing you made it false so you could simulate the error output in the next picture.)

The documentation for .above states:

The aliases .gt and .greaterThan can be used interchangeably with .above.

However, for .least:

The alias .gte can be used interchangeably with .least.

To my mind, there should be a .greaterThanOrEqual alias for .least in addition to

In dareid/chakram#6 (comment) I note the inclusion of the extra word 'comprise' for request assertion chains.

I can't find documentation for this keyword through an API search or elsewhere on the web.

It may be because one of the unfortunate costs of building sentence-like build chains - is that each function is a dictionary word not a distinctive comp

The and method is not supported by Jest, where Chai does support it.

It should probably cut the assertion in two:

- expect(ticketNumber).to.be.above(0).and.to.be.below(46)
+ expect(ticketNumber).toBeGreaterThan(0)
+ expect(ticketNumber).toBeLessThan(46)

Is this a feasible option for codemods?

If so: I'm willing to work on a PR.

With redux-things/redux-actions-assertions-js#3 "with state" function now supports function.
Docs needed to be updated:

• chai
  • Update function definition
  • Add example of usage
• expect
  • Update function definition
  • Add example of usage
• expect.js
  • Update function definition
  • Add example of usage
• should
  • Upd

When following the setup guide, I get this from the sample:

λ node tests\chai.js
C:\Users\User\AppData\Roaming\npm\node_modules\selenium-webdriver\lib\promise.js:2634
        throw error;
        ^

TypeError: checkSizzleExists(...).then(...).then(...).thenCatch is not a function
    at finder (C:\Users\User\AppData\Roaming\npm\node_modules\chai-webdriver\node_modules\webdriver-sizzle\

Is it possible to add support for debugging with the 'npm run dev' command?
I can't see to make it work using --inspect or --inspect -r ts-node/register Index.ts.

Maybe it's some issue with the combination of nodemon and ts-node.
Debugging support make it so easy to debug issues.

Since NaN !== NaN, a NaN value causes containSubset to fail, and the error message is confusing because it looks like it's erroneously complaining about missing fields...

Maybe we should use Object.is or equivalent?

      expect({foo: NaN, bar: 'baz'}).to.containSubset({foo: NaN})

      AssertionError: expected { foo: NaN, bar: 'baz' } to contain subset { foo: NaN }