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

The code example for ReactWrapper's update method (https://github.com/enzymejs/enzyme/blob/master/docs/api/ReactWrapper/update.md#example) is incorrect.

I'll reproduce it here:

class ImpureRender extends React.Component {
  constructor(props) {
    super(props);
    this.count = 0;
  }

  render() {
    this.count += 1;
    return <div>{this.count}</div>;
  }
}

const wr

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)

Hi, I'm a Redux maintainer. I'd like to offer a couple suggestions.

Problem

The current Redux example implementation shows use of reducers with "hand-written" immutable update logic, and has a somewhat complex store configuration. In addition, the project currently uses a "folder-by-type" folder structure.

Proposed Solution

The project should switch to using the official [Redux

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();
  })

Seems useful. Perhaps we add an --inspect flag?

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

Issue :

The Paths Mapping section of the documentation suggests using the native node require but this fails with a Syntax Error when

Expected

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

When I try to run create-react-app samples, it doesn't work

To Reproduce

cd /tmp
git clone git@github.com:smooth-code/jest-puppeteer.git
cd jest-puppeteer/examples/create-react-app
npm i
npm run test:integration

It outputs

@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!

I was noticing that when running jest with the --no-color flag, jest-image-snapshot was still using color. It looks like this is due to code introduced in #5 to solve the same issue that running jest with the --no-color flag would do. IMHO, all colorization should be consistent across all tests and handled at the jest level, not specified per expect() invocation.

Wanted to make sure tha

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

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

Describe the feature you'd like:

Jest-Extended has an assertion named the same as jest-dom'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, the version of jest-extended overwrites the one from jest-dom.

Describe alternatives you've considered:

Maybe an opti

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.

REPL

• needs to be added to API docs as well