notion-sdk-js VS react-relay

Here is an example of how to create a new page in your Notion workspace with the blocks converted from the original HTML. We use the @notionhq/client library and you'll need to have a valid Notion API key and database ID:

Provides data fetching functions that add some utility to the notion-sdk

Thousands of great APIs run their developer hubs on ReadMe, where our customers are already documenting every little detail about their API using the OpenAPI Specification. This got us thinking: “the OpenAPI Specification already provides a ton of valuable information about an API, what if we use this to generate an SDK that’s as good as Notion’s JavaScript SDK”?

The official guide actually suggests to poll all the time and compare to local DB to imitate webhooks.

Here are the links if you need them JavaScript https://github.com/makenotion/notion-sdk-js

Hey, I created a Notion automation in Python that sends an Email to a given recipient when the value of a select property in a Notion database is changed. To send the Email, the SendGrid API is used. I inspired myself at the official Notion node.js implementation.

Go To Documentation

GraphQL Relay is one of the most powerful GraphQL clients that you can found on the web environment. It provides to you a lot of features that lets your development flow in a scalable way.

GQty (https://gqty.dev/) and Relay (https://relay.dev/) will combine fragments or queries you request in your React components and will handle combining these / getting the data each component needs with as few queries as is possible. Are there any other clients I’ve missed? It’s not immediately clear to me whether this is possible with Urql via Exchanges (https://formidable.com/open-source/urql/docs/advanced/authoring-exchanges/).

Inside Woovi, our entire codebase is managed by GraphQL using the Relay client framework. To ensure the best UX possible for our final user, we give some useful features in our payment link, like the real-time update after paying a charge. It's all handled by our GraphQL, which won't be solvable by templates in our use case.

Since you mentioned Node CRUD APIs, I'd probably suggest looking at Relay/GraphQL. Would give you exposure to some interesting and employable skills that wouldn't require you learning an entirely new domain on top of it. They are rewriting the current compiler in Rust, which since you mentioned Rust might be interesting to follow. Uneducated takes, but GraphQL is a schema IDL, so would probably be a good place to start to minimize lexical complexity while still having some cool abstract concepts to learn (interfaces, unions, etc).

You may be familiar with Global Object Identification(GOI), especially if you've used Relay.

Relay (17k ⭐) -> The production-ready GraphQL client for React, developed by Facebook, was designed to be performant from the ground up, built upon locally declaring data dependencies for components.

I think open sourcing for free labor is a common misconception. Most corporate led open source projects (eg, https://github.com/bottlerocket-os/bottlerocket from AWS or https://github.com/facebook/relay from Facebook) still require a team of employees.

If you look at relay.dev, Relay is the GraphQL client that scales with you. This definition is simple and defines Relay pretty well for the ones that already know all the features that Relay brings to the table.

https://github.com/psf/black/issues/338 https://github.com/VeriorPies/ParrelSync/issues/61 https://github.com/prusa3d/PrusaSlicer/issues/5751 https://github.com/iterative/dvc/issues/2530 https://github.com/facebook/relay/issues/3647 And I know godmode9 at one point absolutely freaked when navigating into a symlink. It kinda depends on the app and what it's trying to load