tada
tada copied to clipboard
rafd
a clojure(script) library that helps you compose web-applications out of declarative data-driven parts
Currently, `register-events!` clears any existing events and replaces with the given ones. In the case that all events are in a single namespace, this works fine, because every time that...
Currently, if a tada event is passed parameters with more keys than a spec defines, it silently drops those extra keys (using spec-tools' coercion). This is fine, because it helps...
In some situations, the only time a return value is available would be inside of the `:effect`, for example, creating a db entity and needing to return the id of...
Currently only `:incorrect` and `:unsupported` anomalies are mapped to HTTP status codes. The helper function should handle other anomaly values with different status codes. ``` :unavailable can-retry :interrupted :incorrect 400...
Make a client-side library that can transparently make ajax requests for events & display errors properly based on the anomaly value.
Currently, the `:effect` of an event can perform arbitrary side-effects. It would probably be better if that was contained in some way. One approach would be a re-frame style of...
There is a spec defined for the event conditions, but it currently isn't being used. This is because when the spec is defined, we just know that the params will...