Erik Dakoda

I see there is a lot of activity in the Next.js version of Vulcan. Has there been a new decision made about whether Vulcan will be migrated away from Meteor?

Okay, thank you for the update! I agree with the decision to move most of the code to NPM packages. Then the next biggest hurdle to moving away from Meteor...

Hello, @yairtal and @eric-burel! My recommendation is that you commit the updated Datatable component as a new Datatable2 component and let each dev migrate to it at their own pace....

@eric-burel Wow, this is big! I'll have a look soon. Is this a breaking change, or is it supposed to be totally backwards compatible?

Wow, this is too soon for me. I have dozens of components and 100+ server-side queries that I have to still migrate from `terms` to `input`. I am using the...

@eric-burel Are you able to build and run the unit tests after upgrading to Meteor 2?

Thank you for bringing this to our attention. I say we upgrade to `@apollo/[email protected]` and try the suggested change to `multi2.js`. I would be happy to look at `multi.js` as...

> In the meantime you can implement the "data/previousData" stuff locally with useState. @eric-burel I am sorry, maybe I misunderstand what you are suggesting, but that would require changes in...

Try this: ```javascript collection.attachSchema({ addedField1: { type: Boolean, . . . }, addedField2: { type: Object, . . . }, }); ```

@EloyID there is a bug in `addField` that I attempted to fix with a PR but the change was reverted by @SachaG. Here is our discussion about it: https://github.com/VulcanJS/Vulcan/pull/2648 ....