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

Type of issue: (feature suggestion, bug?)

Suggestion

Chapter:

no-chapter

Why use .jsx instead of .js? It's not a best practice: facebook/create-react-app#87 (comment)

https://twitter.com/TheLarkInn/status/1056729742437543936
https://github.com/reactjs/rfcs/blob/gaearon-patch-2/text/0000-lazy.md

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.)

Is this a bug report or a feature request?

bug

Version Info

• Version of Majestic: v1.6.2
• Version of Jest:
• Version of Node:
• Operating System:

Reproduction Repo

Create a unit test with two describe blocks and each describe block place the a test with the same name.

describe('block 1', () => {
  it('test name', () => {
    expect(true).toBeTruthy();
  })

Current Behavior

For every new project I start with TSDX, one of my first steps is to add stubs for static assets and stylesheets - as detailed on the Jest docs.

Desired Behavior

Add Jest file stubs in to the TSDX setup.

Suggested Solution

Following the Jest docs

// package.json
{
  "jest": {
    "m

While reading docs/readme for this repo, I am analysing the repo for usability of boilerplate. To find meaning of a word, I just google it. But for this one, I need to go deep and I can lost my primary reason for searching for this word. You cannot say RTFM to people if manual doesn't use proper language. #19

I download the ZIP and run npm install but then I run expo start and I get:

[11:17:11] Starting project at /Volumes/Sata/repositories/snowflake copy
[11:17:12] Expo DevTools is running at http://localhost:19002
[11:17:12] Error: Missing app.json. See https://docs.expo.io/
[11:17:12] No Expo configuration found. Are you sure this is a project directory

How I solve this?

Th

🚀 Feature Proposal

Jest has a new package @jest/globals in v25.5.0 which Jest's globals can be explicitly imported.

The introduction of this new package also led to the change of hoisting in babel-jest plugin. We also need to do the similar thing, referencing Jest PR facebook/jest#9806

Motivation

To make hoisting behavior not different between `babel-

Hello,

I would love to see some instructions on how to get this generated file/folder structure skeleton to work well with google/clasp's set up, specifically where to place its .clasp.json, appsscript.json, etc, relative to the src folder of typescript-library-starter, so that clasp push would work perfectly.

TIA, and good work!

• Platform: MacOS
• Mercury Parser Version: master
• Node Version (if a Node bug): v11.1.0
• Browser Version (if a browser bug): n/a

Description

I have created a custom extractor for https://www.gruene.de/themen/arbeit which delivers the expected results for content and lead_image_url with the following specifications:

export const WwwGrueneDeExt

🐛 Bug Report

Using jest-dev-server, set a command like:

module.exports = {
  command: 'npm run start',
  launchTimeout: 1000,
}

If the timeout occurs, you get this message:

Server has taken more than 1000ms to start.

The problem here is that jest-dev-server then never sends the proper signals to the processes started by the command, meaning they get

@diegohaz - i noticed a couple of minor spelling errors on the main site:

Basic stack
It includes everything necessary to build a tipical web app with focus on productivity and developer experience.
Learn more about the recomended workflow

Should be typical, and recommended.

Just an FYI.

Thanks!

vue-tooltip component sometimes is hidden because of the overflow of the parent element (i.e modal)

.

Hi,

Checking out the preview book on O'Reilly, I ran across a small issue with the initial recipe.js example under "Break Components into Modules".

import React from "react";

function Recipe({name, ingredients, steps}) {
    return (<section id="baked-salmon"><h1>{name}</h1>
        <ul className="ingredients">        {ingredients.map((ingredient, i) => (
            <li key={i}

🚀 Feature Proposal

This debug button is present when the test fails and this works nice.

Lately I've been writing a lot of tests and some of them were green although they weren't supposed to be. It would be great if the debug button was there when the test was successful.

As a workaround i just add a fail() and wait until the test fails, then i can debug it.

📷 Screenshots

The

Some folks have noted it would be beneficial to have this repository translated to other languages. One contributor has already volunteered to translate the repository into Russian (woohoo!).

If anyone has the time and drive to help out with other languages, please reply below with the proposed language and I'll give you the "go-ahead"... just to make sure two people don't create translations i

Describe the feature you'd like:

Being new to testing-library, it all is a bit overwhelming. The long list of matchers jest-dom introduces, also makes it harder to start out.

Suggested implementation:

Group the matchers in the documentation over some headings, e.g. “Checking element existence”, “Checking forms”, “Checking element state”.

Describe alternatives you've cons

I can obtain record list (in JSON) from server.
jsonTypes handler passes if record list is filled with designated items.
However jsonTypes handler seems to disallow empty record list: Expected '*' not found (path 'records.*')

repro/test.js:

const frisby = require('frisby'),
  Joi = frisby.Joi;

it('should pass', (done) => {
  frisby.fromJSON({ records: [] })
    .inspectBody()

Points to cover:

• playbook for how to get started with testing
• differences between testing locally vs staging vs production
• how to configure tests for different environments

@johngrimsey thank you for the idea! Please feel free to comment if I missed something.

It looks like sendgrid is currently only used to reset user passwords. If that is the case it would be nice to have it also used to send a confirmation email upon user registration, so that it can be properly validated.

I suppose this would require the use of a unique email validation token.

Describe the feature you'd like:

Jest-Extended has an assertion named the same as jest-extended's one:

-> https://github.com/jest-community/jest-extended#tobeempty
-> https://github.com/testing-library/jest-dom#tobeempty

When both libs are used in the same project, in my case the version of jest-extended overwrites the one from jest-dom. But this might vary depending on the order use