warn for invalid keys for components

[indam23]

Proposed changes:

• Warn when a user provides a key for a component that is not part of the component's allowed keys
• closes Warn for invalid keys for classifiers #6966

Status (please check what you already did):

• added some tests for the functionality
• updated the documentation
• updated the changelog (please check changelog for instructions)
• reformat files using black (please check Readme for instructions)

Should this raise InvalidConfigError instead, the way validate_requirements does?

[wochinge]

Thanks for taking this over 🙌

[wochinge]

can we add the link to the documentation for Components please?

[wochinge]

Note that this may raise an exception. Maybe it would be better to run the validation within _build_pipeline?

[wochinge]

Or even better within component.create_component?

[wochinge]

that would also avoid having to do the check in two locations?

[indam23]

mm I tried moving it into component.create_component, but in that case extra keys are present that aren't allowed for the child class, but are for the base class (e.g. intent_classification is present for ResponseSelector). So, it isn't only checking the user-provided config at that point.

Re. putting it in _build_pipeline - you mean moving the logic inside the function instead of calling it from there? Which exception would that avoid?

[wochinge]

it would have the advantage that you don't have to load the components yourself in _build_pipeline (which can go wrong and then you'd need error handling).You'd already have the instantiated components in _build_pipeline which should simplify your validations.

[indam23]

I moved it - does that work?

[wochinge]

Couple of smaller suggestions. Please have look. Looks good otherwise 🚀