Create script to gather linting errors in SDDS components

Update to include running coder as well and update links.

This private repo can be used until we are ready to make it public:

https://github.com/salsadigitalauorg/starshot_demo_validator

@jacobadeutsch Let's repurpose this one to be more general. We can talk through it. Marking postponed for now.

Kristen Pol → credited jacobadeutsch → .

Updating issue to be more generic.

Add link.

Here is the current version of the megalinter, it runs in the demo design system directory and can take a directory as an argument, but it defaults to the components dir and the starshot_demo/components dir

Thanks. I’ll review this and we can split out the ui patterns validation

We should get this code into this repo or another one. It seems to be working as needed so not too worried about the structure/style of the script.

Note that it was used to find issues that were manually fixed as part of this issue:

📌 Use SDC conversion script to create baseline SDC YAML and README files Fixed

This is an issue that was created out of this work that has been fixed:

🐛 Component TWIG Warnings for Field and Grid Fixed

These were the results from the linter that Jacob sent me. He fixed most of these manually before doing the baseline files in:

📌 Use SDC conversion script to create baseline SDC YAML and README files Fixed

This is good enough for this issue. We'll do a follow up focused on the UI Patterns validator.

Note we decided note to update:

warning missing document start \"---\"

because core doesn't use that at the start of YAML files.

He fixed the 80+ chars and the here should be 0 space after the hash values errors.

The Unused variable warnings were fixed per #12.

Automatically closed - issue fixed for 2 weeks with no activity.