effect
graphql-spec
| effect | graphql-spec | |
|---|---|---|
| 25 | 37 | |
| 5,057 | 14,226 | |
| 22.5% | 0.2% | |
| 9.9 | 5.8 | |
| about 1 hour ago | 26 days ago | |
| TypeScript | Shell | |
| 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.
effect
-
Exploring Effect, a meta-state RxJS-like framework
Effect is a functional library for building and composing asynchronous, concurrent, and reactive programs in TypeScript. It focuses on providing a robust and type-safe way to manage side effects in your programs.
-
A better way to handle errors in JavaScript
Just use a library that already contains this and more functional programming idioms, like fp-ts or its successor, Effect [0]. It is a little more complex to learn but much more robust that simply implementing your own Result and other types.
[0] https://www.effect.website/
- opinions about Effect-TS, do you recommend using it? when to use it? When to avoid it? not worth it?
-
Building React Components Using Unions in TypeScript
effect-ts
- Effect - A set of libraries to write better TypeScript
- Effect – A set of libraries to write better TypeScript
- Effect-ts: a library for writing ZIO-like effect-based applications
- Effect, a functional effect system for TypeScript with a rich standard library
- Effect: A functional effect system for TypeScript with a rich standard library
- Alternatives to scala FP
graphql-spec
-
Show HN: REST Alternative to GraphQL and tRPC
GraphQL's first draft release was 8 years ago. [1]
It's first non-draft release was 5 years ago. [2]
It's first release under a community foundation was 2 years ago. [3]
[1] https://spec.graphql.org/July2015/
[2] https://github.com/graphql/graphql-spec/releases/tag/June201...
[3] https://github.com/graphql/graphql-spec/releases/tag/October...
-
Intro to PostGraphile V5 (Part 3): Introspection and Abstraction
I'm a big believer in GraphQL (in fact, at time of writing I'm #2 contributor to the GraphQL spec itself) so it pains me that a tool I built doesn't always have easy ways to achieve the "versionless schema" design that GraphQL encourages when it comes to making significant breaking changes to your underlying database tables. (Personally, I think you should aim for your database schema itself to be versionless, but this is not always possible.) Of course you can build your PostGraphile schema over views instead of tables, but views have their own problems that I won't go into here…
-
Migrating Netflix to GraphQL Safely
I created a proposal for Map type but didn’t make it through.
https://github.com/graphql/graphql-spec/pull/888
The issue with GraphQL is it tries to appease too many masters.
Similar to jsx. The language isn’t evolving.
The good thing is the spec is (almost) frozen, so there’s many implementations, the bad is it can encompass the flexibility of json schema can do.
-
GraphQL Live Queries with live directive
Longer thread - Subscriptions RFC: Are Subscriptions and Live Queries the same thing?
https://github.com/graphql/graphql-spec/issues/284
-
Ask HN: Tutorials Written with Heavy Dependencies
You’ve probably figured it out by now, but for others who may be in a similar position; GraphQL is a specification (with various implementations) and you can read up on the spec here: https://spec.graphql.org/
-
GraphQL object schemas - how to represent (and query?) Graph (hierarchical objects) in GraphQL?
If you're asking whether GraphQL supports anonymous objects that can be arbitrarily nested then no, it doesn't.
- Union for an input to a mutation arg
-
Thanks graphql, I hate it.
show this feature request some love https://github.com/graphql/graphql-spec/issues/174
-
Deprecation Notice: GraphQL for Packages
* Performance: It's just hard to track down what makes an operation slow. The waterfall nature of resolvers is a big contributor
[1] https://github.com/graphql/graphql-spec/issues/488
-
GraphQL error handling to the max with Typescript, codegen and fp-ts
:::note GraphQL Union is available for Types only, not for Inputs. However, the oneOf directive will bridge the gap in the future.
What are some alternatives?
fp-ts - Functional programming in TypeScript
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.
pratica - 🥃 Functional Algebraic Data Types
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
tyrian - Elm-inspired Scala UI library.
graphql-ws - Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client.
contentlayer - Contentlayer turns your content into data - making it super easy to import MD(X) and CMS content in your app
Neo4j - Graphs for Everyone
eslint-plugin-functional - ESLint rules to disable mutation and promote fp in JavaScript and TypeScript.
graphql-shield - 🛡 A GraphQL tool to ease the creation of permission layer.
Index - ⚡ Pattern Matching in Typescript
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)