fquery
TypeGraphQL
Our great sponsors
fquery | TypeGraphQL | |
---|---|---|
5 | 30 | |
10 | 7,934 | |
- | - | |
0.0 | 8.8 | |
over 2 years ago | 4 days ago | |
Python | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fquery
-
Solving the double (quintuple) declaration Problem in GraphQL Applications
Similar benefits without codegen (based on decorator magic) for a python based stack:
https://github.com/adsharma/fquery
* Use dataclasses for both database schema and the user facing operations
- Cut Out the Middle Tier: Generating JSON Directly from Postgres
- Against SQL
- Django for Startup Founders: A better software architecture for SaaS startups
-
SwiftGraphQL – A GraphQL client that lets you forget about GraphQL
Re: Conways law at Facebook
I was at Facebook when GraphQL was invented, maintaining a backend storage service where a core assumption was that storage should be reorganized based on access patterns and that predicates should be pushed down to storage where they can be executed more efficiently.
GraphQL was hard to push predicates down, because you don't know which of the edges were written in PHP.
My response was fquery[1], which is like what's being discussed here but with python as the source language instead of swift and amenable to preserving the largest possible query structure for backend optimizers, including SQL optimizers.
It has some early demos converting a GraphQL/fquery into SQL where possible. It should be possible to add enough metadata to fquery to identify if an edge is non-trivial (calls into another microservice) or trivial (can be optimized to a storage backend or SQL).
TypeGraphQL
-
Cerbos + GraphQL: Do not reinvent user permissions
In this tutorial, we're building a simple application which uses Cerbos inside of a GraphQL server. The server is written in typescript and uses type-graphql to create the schema and resolvers, and TypeDI to handle dependency injection.
-
Using modern decorators in TypeScript
Using decorators required setting an --experimentalDecorators experimental compiler flag. Several popular TypeScript libraries, such as type-graphql and inversify, rely on this implementation.
- help wanted: Typescript GraphQL Types Response
-
Build a Next App with a full GraphQL API using just a JSON or CSV file
TypeGraphQL
-
What to use with Apollo Server v4 to achieve type-safety?
Have you tried TypeGraphQL v2 (it's in beta). Some in this thread have reported success with it.
-
Apollo Server v4 Breaking Changes. Time to move away?
When moving away from Apollo Server, and you're looking for a replacement built with JavaScript or TypeScript, let me give you some options. If you want to keep building your GraphQL API schema first, you might want to consider Mercurius (which relies on Fastify) or GraphQL Yoga. If you're going to build your GraphQL API code or resolver first, have a look at TypeGraphQL or Nexus. Alternatively, there are great GraphQL-as-a-Service solutions such as StepZen in case you no longer want to build, maintain and host your own GraphQL API.
-
A journey towards a type-safe GraphQL API server
There are two main approaches to keeping the types of the GraphQL schema and entities in business logic in sync. You can generate the schema based on your TypeScript code (e.g. TypeGraphQL), or you can generate types based on your schema (e.g. GraphQL Code Generator). We opted for the latter since it slotted right into our existing GraphQL server implementation using Apollo Server.
-
Do you use a tool for generating your GraphQL schema, or do you write it as part of your development process?
I've used tools (e.g. TypeGraphQL) in the past, and for smaller schemas I've just manually written the schema.
-
FoalTS framework - Version 2.9 is here 🎉
Foal's dependencies have been updated so as to support the latest version of TypeGraphQL.
-
Does Apollo GraphQL cost money to use in production? And other beginner questions about GraphQL
Some alternatives to Pothos are https://nexusjs.org/ https://typegraphql.com/
What are some alternatives?
graphql-code-generator - A tool for generating code based on a GraphQL schema and GraphQL operations (query/mutation/subscription), with flexible support for custom plugins.
nexus - Code-First, Type-Safe, GraphQL Schema Construction
graphql-shield - 🛡 A GraphQL tool to ease the creation of permission layer.
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
apollo-server - 🌍 Spec-compliant and production ready JavaScript GraphQL server that lets you develop in a schema-first way. Built for Express, Connect, Hapi, Koa, and more.
pothos - Pothos GraphQL is library for creating GraphQL schemas in typescript using a strongly typed code first approach
Neo4j - Graphs for Everyone
graphql-jit - GraphQL execution using a JIT compiler
Nuxt.js - Nuxt is an intuitive and extendable way to create type-safe, performant and production-grade full-stack web apps and websites with Vue 3. [Moved to: https://github.com/nuxt/nuxt]
seneca - A microservices toolkit for Node.js.
express-graphql - Create a GraphQL HTTP server with Express.
Next.js - The React Framework