Is your feature request related to a problem? Please describe.
As Hubs client add-ons are developed there will need to be a way to add functionality to the Hubs Blender add-on that can easily be distributed/installed.
Describe the solution you'd like
A directory that can be specified in the add-on preferences where a user would be able to put component definitions that the add-on would then load with the rest of the default component definitions.
Describe alternatives you've considered
Adding simple component definitions directly to the preferences and/or a generic component that would allow you to define components by specifying ID and properties. Both of these are expected to be more complex to implement and require more manual work by the user than the proposed solution.
Additional context
A user-specified definitions directory would also make it easier for people to generate/distribute component definitions in general, e.g. for customized instances that are based on code before client add-ons were introduced or instances with changes beyond the client add-ons current API capabilities.
Is your feature request related to a problem? Please describe. As Hubs client add-ons are developed there will need to be a way to add functionality to the Hubs Blender add-on that can easily be distributed/installed.
Describe the solution you'd like A directory that can be specified in the add-on preferences where a user would be able to put component definitions that the add-on would then load with the rest of the default component definitions.
Describe alternatives you've considered Adding simple component definitions directly to the preferences and/or a generic component that would allow you to define components by specifying ID and properties. Both of these are expected to be more complex to implement and require more manual work by the user than the proposed solution.
Additional context A user-specified definitions directory would also make it easier for people to generate/distribute component definitions in general, e.g. for customized instances that are based on code before client add-ons were introduced or instances with changes beyond the client add-ons current API capabilities.