Component Catalog Assistant README

An extension to hook into Lucid's Component Catalog and make it easier to find and fix our frontend components to meet our standards.

The Component Catalog not only documents many of our standardized components, but also includes descriptions of components, CSS classes, or various other HTML structures that have been deprecated or require further review. You can find details on those here.

Features

The Catalog Assistant extension uses data from the Component Catalog to mark your code inline when it does not meet the Catalog's standards.

It also includes Quick Fixes for many of these cases, but it should be noted that the new components don't necessarily have the same fields as the ones they're replacing. Look up the component in our repository to find all the new inputs and properties!

Extension Settings

This extension contributes the following settings:

• componentCatalogAssistant.implementationDefinitionPath: Should contain the path to the component catalog. You do not need to define this in your configuration, since it defaults to the standard catalog path. Only consider setting this config value if you have multiple "main" repositories on your computer and the definitions at ~/lucid/main/component-catalog would be wrong.

Known Issues

Currently the Assistant has somewhat limited ability to transform old components into new components and makes many assumptions about the structure of the data. Our current Catalog does not define any complicated fixes, so this is fine for now, but in the future we may want to clean up the format of the data and make it capable of describing more complex transformations.

Release Notes

1.0.2

Fixed an issue where components were being marked when they shouldn't have been. Updated wording around components that require review by #ufo-eng.

1.0.1

Fixed the content of tags being marked by the Assistant. Now only the opening and closing tags will be marked.

1.0.0

Initial Release.