create new concept map

[bxie]

Replace old concept map with new one and add property of type (semantic, template).

Steps:

1. Create a new branch called "content-quad"
2. Within ConceptMap.js, comment out all of the current conceptInventory constant
3. Create a new conceptInventory constant. This new constant will have the same schemas as the previous except a type property is added to each concept. This type property will either be {concept, template}
4. Populate the new conceptInventory with a concept hierarchy as defined in the image below

Ensure the explanations properties exist but feel free to leave them empty (e.g. empty string, empty list).

Ensure test for parent/dependency in tests/data.test.js passes.

EDIT: Clarifying some ambiguities in requirements

• Have should_teach be true for all concepts.
• Have container be true for all concepts as well.
• Change the world view to display concepts where container is true (currently set to false)
• Add a type onboarding and have the "How Code Runs" concept be of type onboarding. Everything else is of type concept or type template as specified in the figure above.

[kwokwilliam]

Are these all going to have the properties:

should_teach: true
container: true

?

[kwokwilliam]

The plan will be to change the g variable under ConceptAbbreviations.js to support the new grammar labels, and then modify ConceptMap with should_teach and container = true.

[kwokwilliam]

I meant to say container = false. That is how it's being filtered for the WorldView.

[kwokwilliam]

Running yarn test or npm run test puts me into a tool that gives me no tests found.

jestjs/jest#3793 (comment)
This guy pointed out a test difference between mac and windows. I tested with Harshitha's mac and she got further, and was able to find the tests. The tests failed due to something else. Will be looking into this more.

[kwokwilliam]

Currently, I have it such that the parent is the top one (ie data types) and the dependency is the bottom one (ie how code runs). This is seen in the code.

I was a bit unsure about if dependencies was defined as "we need these to have access to this topic" or "this is a dependency of these topics". I believe it is the first after some looking at the existing conceptInventory.

  [g.howCodeRuns]: {
    dependencies: [],
    parents: [g.dataTypes],
    explanations: {
      name: "How Code Runs",
      definition: "",
      examples: [],
      future: []
    },
    should_teach: true,
    container: false,
    type: t.semantic
  },
  [g.dataTypes]: {
    dependencies: [g.howCodeRuns],
    parents: [],
    explanations: {
      name: "Data Types",
      definition: "",
      examples: [],
      future: []
    },
    should_teach: true,
    container: false,
    type: t.semantic
  },

[bxie]

we'll call this jest-related bug for Windows low priority for now until we get to testing next week or week after. admittedly, everyone developed on a mac last summer.

[kwokwilliam]

Got it working! Tests passed too!

Here is what I did:

1. npm install jest
2. npm install jest-cli
3. Modified .babelrc to contain this content:

{
  "env": {
    "test": {
      "presets":[
        ["es2015", { "modules": false }],
        "react",
        "stage-0",
        "flow"
      ],
      "plugins": [
        "transform-es2015-modules-commonjs",
        "dynamic-import-node"
      ]
    }
  }
}

4. npm install babel-preset-es2015

Now I just run jest and it works. It also builds correctly. npm run test doesn't work, though.

Used these pages:
jestjs/jest#3202
babel/gulp-babel#93