[micromanage] Use JSON schemas. Start Collection

Changes the way schemas are parsed such that they use json-schema. It also begins the idea of a Collection domain.

This isn't complete:

[ ] Coverage is low
[ ] I think the CRUD actions should live on the Entity. Then you just have to import one module to get the schema and actions, and it allows a nice separation between data operations and domain definition. It also makes it less cumbersome to use multiple entities in a single domain.

Highlights

import { Entity, Collection } from 'micromanage'

export class Planet extends Entity {
  static schema = {
    title: 'Planet',
    type: 'object',
    required: ['name'],
    properties: {
      name: { type: 'string', title: 'Name' },
      weight: { type: 'number', title: 'Weight', default: 100, min: 0 },
      belt: { type: 'string', enum: ['inner', 'outer'], default: 'inner' }
    }
  }
}

export class Planets extends Collection(Planet) {
  all(matcher) {
    return this.map(Object.values)
  }
}

The neat thing about this is that you can use the schema as an API for other libraries, like form builders:

import React from 'react'
import Form from 'react-jsonschema-form'
import { Presenter } from 'microcosm-dom'
import { Planet, Planets } from '../domains/planets'

export class PlanetForm extends Presenter {
  getModel(repo) {
    return {
      planets: repo.domains.planets.all()
    }
  }

  render() {
    return (
      <div>
        <Form schema={Planet.schema} onSubmit={this.onSubmit.bind(this)} />
        <ul>{this.model.planets.map(p => <li key={p._id}>{p.name}</li>)}</ul>
      </div>
    )
  }

  onSubmit({ formData }) {
    this.repo.push(Planets.create, formData)
  }
}

vigetlabs / microcosm

[micromanage] Use JSON schemas. Start Collection #498

Highlights

Codecov Report