I'll be presenting a new talk, "Magical (or not) GraphQL", at North Bay Python 2024! Introducing a new open source library I wrote for work, how I wrote it, cool things to do with GraphQL, and what I've discovered I want instead of GraphQL. Hopefully the barn cats will be interested too 😻 #Python#nbpy#GraphQL#Flask
mal ne frage
ist es sinnvoll #CRUD operationen über eine #API (ich denke #graphql) durchzuführen?
basically brauche ich eigentlich einen GUI für die #datenbank
ach ja, ich brauche primär keine tipps zur umsetzung, sondern es geht mir primär darum ob bzw. weshalb das konzept sinnvoll ist oder nicht
#GraphQL is the worst fuck I had to deal with, and I dealt with hundreds of shitty APIs but this is just another hyped Meta product forced on devs that is over engineered to a point where all its conceptual advantages are obliterated by complexity.
GraphQL was designed for more powerful and user-friendly client-server interaction. This complex solution is a query language and execution engine. GraphQL is developing quickly and is available as a web service in Drupal 8, 9, and 10. Drupal websites often use GraphQL. This solution is particularly robust as a web service and...
The hyperfocus demon compelled me to go down the #GraphQL rabbit hole again this evening. Been years since I've written any, but I was curious what it would take to make a visualization of a GitHub milestone's issues/PRs over time for a project that I contribute to.
Postman went all in on “enterprise” features a while ago. Now Insomnia is making folks store all their stuff in a cloud account (encrypted but still) and doing a lot of things that are basically following the same route as Postman. Lots of folks are looking for a new REST API & #GraphQL testing client.
#GraphQL and #Strawberry+#Django are a big upgrade from the DRF days, but I still feel like I’m typing the same metadata in 3-4 different places each time I add a field.
Challenge: make adding a GraphQL model as simple as adding a Django admin interface model.
Announcing the launch of InQL 5.x! Our open source #burpsuite extension for pentesting #graphql applications has just gotten even better! We've added several new features to streamline your testing workflows, that we think you'll find useful.
To improve stability and performance, we've started a complete re-write in #kotlin and welcome contributions from the #opensource software community.
Learn more about it in our latest blog post and check it out today!
Here we got a class, in our regular #odata controller functions it produces #camelCase like we tell it to in our settings. However, in our non-base controller function it produces #PascalCase ... because, duck us?
Only on the expanded parts which are handled a little bit differently for efficiency, hense the need for the non-base controller function with odata.
I hate seeing good colleagues leave, and this one really hurt. I just wasnt ready to feel so deflated after building someone up so much.
If you need a very strong backend #django, #graphql, #python and #react#typescript web developer, I know a guy, and we wrote some great, well tested, and typed code
Ok I have to do my usual check with things that seem good:
I'm reading the #GraphQL spec right now and I like it a lot. Are there any reasons why I should not like it or that it is Actually Bad?
thinking specifically in comparison to #SPARQL, which I have heard can be v difficult to host an endpoint, the arbitrary logic can be super resource intensive.
Is the huge additional effort to implement an API with GraphQL support as opposed to a simple JSON/REST model for a moderately complex API (with an SQL backend) in Go make sense?
Exploring the Potential of GraphQL in Drupal Development (gole.ms)
GraphQL was designed for more powerful and user-friendly client-server interaction. This complex solution is a query language and execution engine. GraphQL is developing quickly and is available as a web service in Drupal 8, 9, and 10. Drupal websites often use GraphQL. This solution is particularly robust as a web service and...