• Are you running a release or master: master
• Issue is about a fresh instance (no data in db) or restart: fresh

This seems a known/unfinished issue based on the commented 'Name' field in the code noted below, but I was hoping it could be addressed as it would greatly ease the discovery of the graphql endpoints generated by the db tables as they would become available in GraphiQL in #13

``

If you PATCHed to /posts/1, but send payload with a different id:

{
  data: {
    id: 789,
    type: 'posts',
    attributes: { ... }
  }
}

We pay attention to the payload and not the URL - instead let's throw an error when there is a mismatch.

If you r going to wait response,or block the goroutine in a getty session(tcp conection), task pool can not be null。

func (s *Server) newSession(session getty.Session) error {
	var (
		ok      bool
		tcpConn *net.TCPConn
	)
	
	// 省略部分代码...
	session.SetTaskPool(srvGrpool)
	return nil
}

ortherwise,handleTcpPackage() will blocked,led to the response missing

func (s *session

Currently the module field on package.json points to src/simpla.js but really it should point to a separate build, that's been transpiled, but not bundled. This means that whatever module bundling system consumers are using will still be used, but it won't need to be transpiled. As it currently stands, users can come up against [this bug](https://github.com/facebookincubator/create-react-app

We should have a test that validates each service can actually be resolved from the container (within a scope). See #339 for motivation. It would be fantastic if this could be done via reflection and not manually adding a new test every time you register a new service. I'm thinking we would define a static member that contained all the ServiceDescriptors. Then in the test we just get this member