have the build be able to output / provide a copy of the graph

[hutchgrant]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

We use a mock of our graph to run a large number of unit tests. Everytime we change the graph, our mock graph must reflect those changes or we're testing outdated data. I propose a toggleable function which can be run within graph lifecycle to automatically export a mock of the graph

Details

const generateMockGraph = async (graph, debug) => {
  if (debug) {
    const targetDir = path.join(__dirname, '../..', 'test/unit/data/mocks');
    const targetFile = path.join(targetDir, 'graph.js');
    const mockGraph = 'module.exports = { \n'
    + '  // eslint-disable-next-line \n graph: '
      + JSON.stringify(graph)
      + '\n};';

    await fs.writeFile(path.join(targetFile), mockGraph, 'utf8');
  }

};

[thescientist13]

Gonna tweak the title of this, as I would like to leave open to different options of how to approach this.

[thescientist13]

I think this issue would be great if implemented after #199 in which we establish modes with escalating levels of output / toggling.

Would also need this documented, at least in the CONTRIBUTING.md.

[thescientist13]

I think actually happens now as of the 0.10.0 release? Correct me I am wrong but we do emit a graph.json now, which I believe did not exist before.