2018810 - Mark major components as major; group additional components accordingly

Status: NEW

(Core :: Machine Learning: General, task)

Description

[Bryan]

Currently, there is no obvious marker for a given component to identify it as a major component vs an additional component. In the same way - there is no obvious link between major components and their associated additional components. We should ideally major components in some way (e.g. an additional field in the config or possibly a naming convention) and then associate their additional components (e.g. chat.additional_comonent1, chat.additional_component2, etc).

One possibility is to just do the latter (e.g. major components are called component and additional components are called component.additional_component)

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Core::Machine Learning: Frontend' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.