(feat) Functional API

[dselman]

Signed-off-by: Dan Selman danscode@selman.org

Issue #187

Create a functional API for concerto objects.

Changes

Flags

Related Issues

• Issue #
• Pull Request #

[jeromesimeon]

Most immediate suggestion: please do the work on top of the release-1.0 branch.

I think we may need the validate method to return a new JS object (we are filling in default values, turning ISO 8601 dates into moment objects, etc). -- Alternatively we could separate those things into two passes: one which changes the data representation (e.g., string to date) the other which validates and only fails/succeeds without changing anything).

I would love if those methods would be functional (i.e., validate would not change the input JSON but construct a new one).

[dselman]

Most immediate suggestion: please do the work on top of the release-1.0 branch.

I like the idea of releasing this first for 0.82.x as I think it will help people migrate progressively to 1.0. I don't think it will be too much work to then update this code for 1.0.

I think we may need the validate method to return a new JS object (we are filling in default values, turning ISO 8601 dates into moment objects, etc). -- Alternatively we could separate those things into two passes: one which changes the data representation (e.g., string to date) the other which validates and only fails/succeeds without changing anything).

I would love if those methods would be functional (i.e., validate would not change the input JSON but construct a new one).

Yes, good idea. Should not be hard to implement.

[dselman]

Already merged into release-1.0 branch.