[heft] Implementation of a copy task.

[iclanton]

No description provided.

[octogonz]

@iclanton File copying seems like a "core operation" that belongs in heft.json rather than in a plugin-like config file. Another "core operation" would be executing simple shell scripts. Both of these actions could be triggered based on the same menu of Heft events.

Thus I'm thinking the config file design might be better like this:

config/heft.json

{
  "eventActions": {
    "beforePreCompile": [
      {
        "eventActionKind": "fileCopy",
        "sourceGlob": "src/**/*.md",
        "targetFolders": [ "dist" ],
        "hardlinkInsteadOfCopy": true
      }
    ],
    "afterPostBuild": [
      {
        "eventActionKind": "shell",
        "command": "rundown",
        "args": [
          "snapshot",
          "--script",
          "./lib/index.js"
        ]
      }
    ]
  }
}

[octogonz]

Combining "before/after" and "pre/post" prefixes seems a little odd.

Instead of something like this:

beforePreLunch
afterPreLunch
beforeLunch
afterLunch
beforePostLunch
afterPostLunch

...maybe we could introduce some more intuitive names like:

beforeBreakfast
afterBreakfast
beforeLunch
afterLunch
beforeDinner
afterDinner

Or, the Windows API used a convention sort of like this:

breakfasting
breakfasted
lunching
lunched
dinnering
dinnered

[iclanton]

I can't tell how much of this comment is sarcasm...

[iclanton]

Closing in favor of #2333