apitogo

apitogo copied to clipboard

The users should be able to configure the endpoints that are authenticated.

cristianoliveira

Be more pluggable, like cargo and git does, where if it doesn't find the default command try to execute `bin/apitogo-foo` for `apitogo foo` for instance

cristianoliveira

User should be able to configure a url that the apitogo will request with the provided data. An example of webhook: https://developer.github.com/webhooks/

cristianoliveira

It should have support for WebSocket. Acceptance criteria: As a user, I must be able to create and connect to a channel that emits some json data each X seconds.

cristianoliveira

It would be good to have a configurable routing like: ``` { "posts": "./posts/*.json", "posts/comments": "./posts/comments/*.json" } ```

cristianoliveira

Take a look on this example here: https://gist.github.com/denji/12b3a568f092ab951456 It will need to have a new parameter like `apitogo --https` or something like that

cristianoliveira

There is this implementation. Need to look into it to see how could we implement it in an easy and configless way. https://github.com/graphql-go/graphql

cristianoliveira