Tomek Gryszkiewicz
Tomek Gryszkiewicz
This is a good, easy entry point to contribute!
Crude roadmap to 1.0. May change! The most important is to agree on the API before it Drab reaches 1.0. Features: * [ ] commander/handler test framework * [x] unify...
Now Drab injects its javascript directly into the page. This is why: 1. Drab’s JS are dynamic (EEx), they depends on the configuration: for example they injects only the parts...
In analogy to `execjs`, we could integrate ElixirScript into Drab and write the whole stuff in Elixir only. ```elixir exec socket do Todo.Data.Http.fetch("/api/todo").then(fn(response) -> response.json() end).then(fn(todos) -> todos |> Enum.map(fn(x)...
Rough roadmap to 2.0, moved few API-changing features from 1.0 roadmap, as to be done in the future. * [ ] make Drab small again: non-standard modules as external packages...
* Drab.Query * Drab.Modal Plus: write a guide on how to extend Drab. This must be done before 1.0, as it is a significant API change.
To be done after 1.0.0: * [ ] optimistic updates with Drab.Element API * [ ] render user templates in compile-time * [ ] compress Drab JS templates
Should take all Phoenix phx.new options, to generate a Phoenix project with Drab installed