Found an interesting work-in-progress entitled "elm-postgrest."
The package author published an article describing the design decisions that he considered in starting the project.
One of my recent goals is to separate front and back-ends from each other as completely as possible and to remove pain points in the tool-chain. Elm and stylish-elephants help by adding type-checking via the compiler for front-end work, and elm-postgrest may make it possible in some use-cases to simply treat the PostgreSQL backend as an end-point. Elm is perfectly suited for tasks that call for read-only data display The middleware is based on another project, written in Haskell, entitled postgREST. It turns a postgres Db into a REST API using elm-http and JSON decoders. The elm-postrest package simply connects and issues a query request using a schema and decodes the results. Roles and permissions for the Elm client application are defined in the Db.
No comments:
Post a Comment