vektah

5 ms·

1. 1.▲
   Request smuggling vulnerability found between Amazon ALBs and Go net/HTTP(99designs.com)

   3 points by vektah 7y ago|0 comments
2. 2.▲
   Introducing gqlgen: A GraphQL Server Generator for Go(99designs.com)

   2 points by vektah 8y ago|0 comments
3. 3.▲
   by vektah 9y ago

   graphql is just one representation of your applications data, it shouldn't dictate your models. I'm thinking about adding something that generates a model if it doesn't exist, but after its generated it becomes the users prob
4. 4.▲
   by vektah 9y ago

   I explored going type first before writing this and you could get pretty close. The details get hard though, how do you represent unions vs enums? even knowing what implements an interface? default arguments? directives?
5. 5.▲
   by vektah 9y ago

   I think its still pretty early days, the easy stuff is fine. Once you throw in data loading or subscriptions you quickly run out of docs or find that its just flat out unsupported. I'm hoping to change that though :)
6. 6.▲
   by vektah 9y ago

   Yeah, it takes your schema and your models and generates as much of the resolver graph as it can, then leaves you with an interface to implement for the bits it cant (usually trips back to the db).
7. 7.▲
   by vektah 9y ago

   Yeah, would be more for existing apps that already have a bunch of domain logic.
8. 8.▲
   Show HN: Generating GraphQL servers for Go(github.com)

   172 points by vektah 9y ago|29 comments