Platform, innovation and industry insight.

From your friends at DADI.

15th May 2017

Roadmap Update

We're close to finishing the first release candidate of API Version 2.0 and have started publishing versions to NPM tagged with "edge".

By James Lambie

DADI API

API “Edge”

We’re close to finishing the first release candidate of API Version 2.0 and have started publishing versions to NPM tagged with “edge”. API “Edge” can be installed from NPM using the following command:

$ npm install --save @dadi/api@edge

Note: API Edge should be considered an alpha release and should not be used in a production environment. We make no guarantees that functionality in one release of Edge will be consistent with that in subsequent Edge releases.

The biggest change in Edge to date is the decoupling of database storage from the core. To use Edge, you must install and configure a data connector.

Following install of API Edge, install one of the two current connectors, with the command:

$ npm install @dadi/api-mongodb --save
$ npm install @dadi/api-filestore --save

A configuration file will be copied to your application’s config folder.

Currently available data connectors

Future data connectors

  • CouchDB
  • Oracle noSQL
  • Apache Cassandra

Issues resolved

  • #211: fix composition, not all fields composed for multi-refetene field schemas
  • #260: rename media collection type “mediaCollection” to avoid clash with another product

Issues in progress

  • #251: respond with HTTP 200 at application root
  • #257: improve composition performance
  • #265: validate arrays against collection schemas

DADI Web

As with DADI API, we’re close to releasing an “Edge” version of Web. This version (which will become ultimately v3.0) will have support for multiple template engines which can be installed independently of the core Web application. Initial template engines under development include Dust.js and Pug; Web v3.0 will be released with documentation for building your own template engine adapter.

Issues in progress

  • #165: find matching roots after all middleware functions pass
  • #163: allow pages and partials to exist in subdirectories
  • #103: support multiple for template engines

#roadmap-updates