When generating a component, the users now have the option to wrap them around with a container.
When the user wants to wrap them with a container: First, the component is generated under lib/components. This component is a purely react component, and has no code related to Vulcan or Meteor. A file with the same name as the component is generated under the lib/containers/ directory. This file imports the said component. The user will have the option to add meteor and vulcan related code here, including registering.
Implication: the only way for a component to be registered to Vulcan, is for it to be wrapped around by a container.
Justification
This restriction forces the users to completely separate representational components from meteor & vulcan related code, effectively making it easier to eject in the future.
Since the representational components won't have any meteor / vulcan related code in them, we can start using react storybooks.
Overview
lib/components. This component is a purely react component, and has no code related to Vulcan or Meteor. A file with the same name as the component is generated under thelib/containers/directory. This file imports the said component. The user will have the option to add meteor and vulcan related code here, including registering.Justification