Eric Burel

It's more a starter, `boilerplate` have a notion of not really being updateable contrary to "starter kits". But that's vague anyway, I say that because we currently alreay call the...

That's a way indeed, you would define your component as a closure: `const SmartForm = components => (props) => {...}` so you can pass different type of components Currently the...

Great to know, I am currently waiting for next Storybook 6.x release, that stabilizes the issues we currently have when React versions are mismatching, before updating Next and React (should...

Quote from Halima Olapade on Slack that might explain this issue: "I think i figured out why the inbuilt voting is breaking. It's cause the Vote collection schema has a...

Voting is handled in the `vulcan:voting` package. Help is welcome to fix this issue. We probably won't be able to maintain such packages in the future, voting looks simple but...

Tagging @SachaG I've investigated and the issue is that this part of the code is just not up to date. Some fields have been deleted in the `packages/example-forum/lib/modules/users/custom_fields.js` but not...

We would be really happy to take PR from contributors on this part, because maintaining those packages can be time consuming while we already have a lot of work on...

Yeah we can merge indeed, 1.1.6 is published. Sorry for those kind of discrepancies, I don't have a live Vulcan app currently so it takes me more time to test...

Hi, do you use a 2 repo install? It's because we are in the process of updating Vulcan. @SachaG can you please publish the latest Vulcan devel packages? I don't...

Hi @TomFreudenberg , we use Vulcan only on existing projects (Live for Good platform for me, and Sacha has his own projects like Sidebar). I don't really advise to start...