Giovanni Gonzaga

Hi @FrancescoCioria , infinite scroll is definitely an interesting case (do we have an internal use-case for this already?) Just to be clear, simple pagination instead works OK as is,...

The use case makes sense to me, and I think adding an `alternative` operator would be pretty straightforward 👍 (EDIT: pushed a quick POC here: https://github.com/buildo/avenger/commit/5e74a82cd920b21e65c6322ce07c176bcc562ad7) As a side note,...

> I would love to compose them so that if the first one is pending or returned an error, the result of the second one is returned Actually re-reading this...

It has since been changed to a Semigroup, renamed to `keepQueryResultSemigroup` and re-exported (see https://github.com/buildo/avenger/pull/223) This issue remains valid for the README part

@giuscri could you suggest a good place to add such a hint in the current README?

Let's discuss this better offline probably, but as a TL;DR of what I got and what actions we could try: - `queryStrict` should only be used for primitive input values...

We re-discussed this offline and came to the following conclusions: - as an alternative to my proposal above "This could probably be added to the signature and enforced at compile-time...

Hi, first of all I'm glad you enjoyed reading through! A few notes (both pros and cons) that you might find interesting: - compared to apollo (and same goes for...

(we already had this discussion offline but I'll add it here too) Seems feasible/reliable, although maybe a bit over-complicated (in the end the multi story one is not our standard...

just bumped into this related work so I'll leave it here https://github.com/fritzvd/standard-version/blob/3116e4fdab3bf43bf7aca3206e1053dd9f61d444/README.md#release-on-a-seperate-branch-like-release20-or-hotfix-parsing-lists