Eric Burel

A small part that would need a refactor is the `newsletter` system. It relies on a Meteor package while we should be able to do the same with Node `cron`...

Hi @ErikDakoda , We have indeed started to migrate toward Next, as a replacement to Meteor. Note that we will have to keep Meteor around for a while, we have...

What triggered this migration is the addition of API routes in Next in v9, which makes it an hybrid framework, supporting both full-stack and pure frontend usage.

Regarding accounts we've introduced GraphQL endpoints in the latest release, so in the backend we don't depend on Meteor. We lack the UI at this point though, and support way...

Not sure where I listed the relevant issues in Apollo, maybe here: https://github.com/VulcanJS/Vulcan/issues/2381 Basically the cache update system is architectured so that mutations are responsible to update queries. But that's...

According to the code from your PR, this is a backend issue => the multi resolver is sending the same item twice, as if the limit was taken into account...

@GraemeFulton will be fixed by https://github.com/VulcanJS/vulcan-npm/pull/56/files (edit: released just now in "0.2.1" of react-hooks) @IBRAHIMDANS the issue is that variables are not correclty merged in the hook, so in the...

Probably a regression. We probably should test `typeof foo.limit === "undefined"`, so both `limit:null` and `limit:0` allow to bypass the limit.

Is there anything blocking this PR? If this works ok in your app I'll merge. Is sorting still ok since `orderBy` is removed as you said?

I don't really have any environment to test so that's why I prefer to "blind merge" if you run it in production already. The breaking change is ok here, old...