via @amycheng: For {{default alpha beta}}, if alpha is ‘’, it will render the empty string

We'd like to use include and export in helpers, but the readme generator cannot handle es2015 modules. Update the generator (or find some way to precompile them on the fly) to handle this.

Note: Make sure the JSDoc parser can understand comments on the export default function

Should this be in the NYMag Handlebars repo?

What's the timeline on the fix?

With layouts being a top level data structure, we need to namespace layout/component templates. This means some helpers will need to reference the namespace + component name rather than just the component name.

For example: https://github.com/clay/handlebars/blob/master/partials/component-list.hbs#L2

Only some of the conditional helpers (if, compare, module) are inline.

It would be more consistent if the rest of the helpers (ifAny, ifAll, ifNone, unlessAll) had an option to be used inline, too.

similar to this comparator, but should include modulo

• remove nymag-specific helpers
• rename to clay-handlebars
• move to clay org

• see if there's a library for this already
• at the very least we need includes

do it like handlebars-helpers does, using verb

Setup

In your package json have two different packages which both depend on clayhandlebars (for example amphora-html and amphora-amp) and within each of those packages have something like the following:

var clayhandlebars = require('clayhandlebars'),
  hbsEnvironment = clayhandlebars();

Expected Result

The two packages should have non-conflicting hbsEnvironments, i.e that hbsEnvironment in both packages should be a separate Handlebars environment

Actual Result

Both packages have the same hsbEnvironment meaning they can potentially conflict when defining partials or helpers. I believe this is due to the fact that clayhandlebars will define the environment by just requiring the handlebars package (which will get cached by require). This causes an issue if the two packages intend to add partials of the same name

Possible Resolution

One possible resolution I think would be to make a slight modification to the way the environment is created. In the initialization method change the handlebars initialization to use create so that it always produces a no-conflict handlebars environment to use.

right now I'm using my standard linting, but we should add it (and coverage) into the repo

date-fns is a moment-like library that gives us more modularity and a smaller bundle size:

• ability to require individual functions, similar to lodash v3+
• no need for webpack localization hacks
• equivalent api for the things we use moment for