|elm-version||0.16.0 <= v < 0.17.0|
|Committed At||2016-04-30 18:55:55 UTC|
Pylon is currently growing rapidly and organically to facilitate completion of our project on time. Some good, bad, and ugly is present, but overall the foundation is much better and cleaner than Scaffold was. Since our minimum viable product development phase is nearly over with, Pylon will be getting a much needed major overhaul over the next full two months.
The new version of the API will be more completely founded on the
App.chain pattern that is really
wonderful for dispatching side effects in a fluent way and do away with the Group, Data, and
Resource types altogether. A new API has been designed that treats the database connection as a
single active JSON record maintained by a data structure designed in the following way:
DB.Recordcontains a version history that spans the time between the last external update and now.
open(open current path),
openr(open current path recursively),
close(close current path), as primitives for manipulating the active record's scope and subscriptions.
More news on the development of this system later. There should be a single commit by mid to late May.
NOTE : Pylon.Tree has been removed.
The big experiment, Scaffold, has been pruned to it's most useful essentials, and the database API has been exposed. This takes only the best architectural features from Scaffold, leaving a much more workable interface with very little bloat to work through. Scaffold lives through Pylon, the refined and heavily pruned addition. Pylon does not suffer from the same horrible type bloat and takes much better advantage of the Elm Architecture overall.
~Examples will be coming very soon, within two weeks. Enjoy!~
TODO : Write a variation of the Elm Architecture Tutorial which gently introduces the many helpers provided and culminates in building a simple but fully fledged application against Firebase using Pylon and ElmFire (with deepest appreciation and love to Thomas Weiser for his amazing work).