View Code? Open in Web Editor NEW

generate ORM, GraphQL backend and React JS frontend to CRUD against your database schema

License: MIT License

Makefile 0.77% HTML 0.52% CSS 0.23% JavaScript 16.16% Go 7.49% Smarty 33.93% Shell 0.14% Elm 40.77%

Summary

Uses sqlboiler to generate ORM, GraphQL backend, React JS frontend, and Elm app to CRUD against your database schema

Getting started (Docker)

docker-compose up

once you see

graphql_1   | 2018/04/13 05:16:44 Listening at :5000 ...
web_1       | You can now view hellocrud-js in the browser.
web_1       |
web_1       |   Local:            http://localhost:3000/
web_1       |   On Your Network:  http://172.19.0.2:3000/
web_1       |
web_1       | Note that the development build is not optimized.
web_1       | To create a production build, use yarn build.

Generated React app http://localhost:3000/
Generated Elm app http://localhost:4000/
Generated GraphQL endpoint http://localhost:5000/graphql
GraphiQL interface http://localhost:5000/graphiql

Omakase

GraphQL https://graphql.org/
Go GraphQL https://github.com/graph-gophers/graphql-go
Go ORM builder https://github.com/volatiletech/sqlboiler
Go DB migration https://github.com/mattes/migrate/blob/master/cli/README.md
Javascript form https://github.com/final-form/final-form
Javascript GraphQL https://www.apollographql.com/docs/react/
React https://reactjs.org/
Elm http://elm-lang.org/
- krisajenkins/remotedata
- NoRedInk/elm-decode-pipeline

hellocrud's People

Contributors

Stargazers

Watchers

hellocrud's Issues

Add templates to generate `elm/`

if the result is good, then js/ will be deprecated

Add a way to do role-based authorisation

React JS code should destruct the `props` -- it's cleaner

Setup CI

then we can test generating of code, and tests of generated code

Move away from using standard sqlboiler generator for non-orm files?

Type conversions from Postgres to GraphQL is a very distracting chunk of the templates. Wondering if we should have our own cli (using sqlboiler lib nonetheless) to encapsulate them better, and declutter the templates.

A cursory look at sqlboiler main.go doesn’t turn up an easy place to start plugging in...

OpenCRUD

https://github.com/opencrud/opencrud

Consider `userErrors`, separate from top level `errors`

Ref https://gist.github.com/swalkinshaw/3a33e2d292b60e68fcebe12b62bbb3e2

Rule # 22: Mutations should provide user/business-level errors via a userErrors field on the mutation payload. The top-level query errors entry is reserved for client and server-level errors.