notion-sdk-js VS generator

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

I find straight forward, dedicated combinators much more readable and practical to use ie. for iterables (context where it makes a lot of sense) [0] example [1], runtime assertions (through refutations, which are much faster than combinators over assertions) [2], parser combinators for smallish grammars [3] etc.

In many cases vanilla/imperative js is more readable and terse, no need to bring functional fanaticism everywhere, just in places where it gives true benefits and in form that can be understood by peers.

Functional code can be beautiful and can also be unreadable/undebugable. Same with imperative code. It's great in js/ts you can pick approach where the problem is expressed more naturally and mix it at will.

[0] https://github.com/preludejs/generator

[1] https://observablehq.com/@mirek/project-euler

[2] https://github.com/preludejs/refute

[3] https://github.com/preludejs/parser

You can type it, take a look at pipe and pipe1 in [0].

[0] https://github.com/preludejs/generator/tree/master/src

Loops are great if your programming languages supports iterables/iterators/generators (also async generators) like in js/ts for example.

Especially generator-to-generator combinators ie. [0] give you terse, transducer expressiveness over computation on finite/infinite streams, arrays, etc. (all iterables). It's easy to compose them, jump into for loops if needed for arbitrary yielding (ie. yielding multiple items sometimes, skipping some, halting etc). `continue`, `break`, nesting, yield, yield from, normal code in for loops is very intuitive and terse creating pleasant, understandable code.

[0] https://github.com/preludejs/generator