keechma / forms

Form engine for ClojureScript apps

Keechma

Keechma is a micro framework for Reagent written in ClojureScript. It gives you a set of utilities that allow you to build applications that have the following properties:

• Deterministic and predictable behavior
  • Based on the route, you can determine what the application's state will be
  • UI never "requests" data it's always provided to it
• Unidirectional data flow
  1. Route params are derived from the URL
  2. Application state is derived from the route params
  3. UI is derived from the application state
• Loose coupling between components
  • Communication is performed through core.async channels
• Automatic synchronization of entities' states
  • An entity is any data loaded into the app that has an identity (e.g. :id column)
  • Entities are stored in the EntityDB
  • EntityDB propagates entity state to every place where that entity is displayed in the UI
• Enforced lifecycle (and memory safety)
  • Automatically load data on route change
  • Automatically clean up stale data on route change
  • Automatically set up event listeners on route change (e.g. listener on the WebSocket)
  • Automatically tear down event listeners on route change
• Applications are first-class citizens
  • Applications can be started and stopped
  • Applications can be passed around
  • Applications can mount sub-applicationsns
• UI components are decoupled and reusable
  • UI components can declare it's dependencies
  • Dependencies are injected when the application is started
  • Each component has own context
• No shared globals
  • Router is bound to the application context
  • App state is bound to the application context
  • Multiple apps can run at the same time, each with own state

Documentation

Read the guides or the API docs to find out more about Keechma.

Name

Kičma (lat. columna vertebralis) is a Croatian word for backbone / spine.

Yes, it’s a nod to BackboneJS and SpineJS.

License

Copyright © 2016 Mihael Konjevic.

Distributed under the MIT License.

forms's Issues

Is there a way to do validations where the validation depends on two form fields?

Example: password and password confirmation being equal?

Dynamic forms

I need to create a form with dynamic fields. For example, there is a project form. I select project type and then I see different fields depending on project type. I didn't find how I can do it with this library. Now I can only separate this different fields to different forms and create required form when select project type. But that's not convenient.

Remove runtime dependency on lein-doo

I think the lein-doo dependency is only needed at test time, not at runtime.

The problem manifests itself in combination of figwheel 0.5.4-5 and keechma/forms:

In my project I'm using figwheel version 0.5.4-5, which has a new behaviour: If a request asks for the resource path '/' it looks for 'public/index.html' resources in the applications classpath. Since it currently finds the 'index.html' in lein-doo it never calls my own application handler, hence I never get the chance to create my page.

Add test for multiple validators in deeply nested validations

Something like this should work:

{:contacts.*.percentage [:0>100 :not-nil]}

Validator functions should receive the whole object as the second argument

Transitive dependency issue with `lein-doo` in dependencies

Issue

First off, great form library. You saved me at least a couple weeks of work with this lib. I'm currently using it one of my projects and noticed that the built in figwheel server cannot server up the proper index.html due to a transitive dependency from lein-doo.

Here are 2 references:

Shows a discussion w/ someone specfically saying they also had the issue with forms lib

bhauman/lein-figwheel#428

Shows an issue in the reagent-template build due to lein-doo in deps

reagent-project/reagent-template#128

Solution

Remove lein-doo from project deps