Skip to content

Restrict component usage by configuration file #23

@thanethomson

Description

@thanethomson

At present we can freely entries for components that potentially don't exist (i.e. allowing for spelling mistakes, or even the use of components in projects where components are generally not used).

This should be restricted by way of the configuration file, so that an error is produced if:

  1. no components are defined and a user tries to add an entry for a component, or
  2. the user tries to add an entry for a component not defined in the configuration file.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions