[FEATURE REQUEST] Validate and add snippet to `devicon.json` in VS Code

[lunatic-fox]

I have searched through the issues and didn't find my problem.

• Confirm

Problem

In devicon.json, we can sometimes miss a property or even get confused about the value that should be added.

Possible Solution

I think many users use VS Code or GitHub Codespaces. Also I got inspired by @BenSouchet comment in order to create a validator and a snippet for a new entry to devicon.json in VS Code.

This is the link to a branch with this proposed feature.

Feature overview

Once you start typing new on devicon.json the snippet suggestion is activated.

Hitting Enter will create a template object with all required properties.

The validator will be working, that's why some parts are underlined in yellow.
If you hover over some property it'll show a short description.

All descriptions were based on Updating devicon.json.

versions.svg, versions.font, aliases[].base and aliases[].alias show autocompletion suggestions with all possible icon versions.

aliases[].base and aliases[].alias are suggested properties, because the objects of aliases are optional.

Validation

• name - ^[0-9a-z-]+$
• altnames[] - none
• tags[] - tags-enum.json

  Needs to be standardized!

• versions
  • .svg[] - icon versions
  • .font[] - icon versions
• color - ^#([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$

  Can be standardized to six digits!

• aliases[]
  • .?base - icon versions
  • .?alias - icon versions

Additional information

I made tags-enum.json just by grouping all existent tags in devicon.json develop branch with Node.js.

I think in a strategy of breaking tags by -, / and space in order to be just a set of single words. But I need opinions on that!

[Snailedlt]

Looks awesome! Ship it! 😁
The tags probably need to be reworked though, but that can also come at a later date :)

[lunatic-fox]

Hello there @Snailedlt!
I agree about reworking on tags, but I think this is long term discussion.
I'll be making a derivative branch using the generic validation of type on tags, that way may be possible to add the other functionalities, while tags is not yet standardized.

[lunatic-fox]

vscode_intellisense_no_tags [deleted by accident] branch.

• tags property has a generic validation against string type
• aliases property has validation to its inner objects

[Snailedlt]

Couldn't agree more! I think we should use the one you made with the tags though, makes it easier to add more tags, and refactor them later on :)

[lunatic-fox]

Great! 🤩
So later I'll be doing a pull request of the first branch with the updates of the second one.

[Snailedlt]

Great! Can't wait to get this merged! Will be a huge improvement, and surely speed up the process both for code contributors and reviewers! 🚀