https://github.com/object88/golang-relay-todo-modern

Classic Todo app with React & Relay Modern front end and Golang backend
https://github.com/object88/golang-relay-todo-modern

golang graphql react relay-modern todomvc

Last synced: about 1 month ago
JSON representation

Classic Todo app with React & Relay Modern front end and Golang backend

• Host: GitHub
• URL: https://github.com/object88/golang-relay-todo-modern
• Owner: object88
• Created: 2017-06-01T03:03:33.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2023-01-24T18:56:42.000Z (almost 2 years ago)
• Last Synced: 2024-04-28T08:04:20.793Z (7 months ago)
• Topics: golang, graphql, react, relay-modern, todomvc
• Language: JavaScript
• Homepage:
• Size: 563 KB
• Stars: 4
• Watchers: 1
• Forks: 1
• Open Issues: 16
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Golang Relay TodoMVC

This is a experiment to merge the front-end part of the [`todo-modern`](https://github.com/relayjs/relay-examples/tree/master/todo-modern) relay example with a Golang [GraphQL / Relay implementation](https://github.com/graphql-go/relay).  I wasn't sure whether the graphql-go implementation would work with relay-modern, and it does.

This project would not happen without extensive pre-existing code from [Facebook](https://facebook.github.io/relay/) and the above projects.  When I figure out what the proper attribution should be, I will add it.

# Setup

This project is set up to use [yarn](https://yarnpkg.com/en/), but NPM should work as well.

There are two setup steps: building the schema file, and building the go server:

* `yarn run update-schema`

* `yarn run build`

Once these are complete, you can start the servers.

# Running

The Go Relay server is set up to start a node process running the front end web server, so you only have to start one process:

* `yarn run start`

Once this is started, you can navigate to `http://localhost:3000`.

All debug messages from both services should log to the console.

Ending the Go process will stop the node process as well.  Note that if the node process is stopped independently, the go process will not notice, and will not restart it.  The node service must be running, because it proxies all GraphQL requests to the GraphQL service.