[FEATURE REQUEST]: split up devicon.json

[Patrik Wehrli]

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

• Confirm

Description

I had this idea before, and was reminded by the check-bot comment in #2135
I am not sure if this works for the whole build and release process, so i guess this needs more input.

The Idea:
Split up the devicon.json into snippets for each icon. So instead of having one huge json, split it up into a "one json per icon"
So in the example case of the teleport icon, we would have a folder like the following:

So each icon folder also includes a devicon.json or teleport.json (whatever fits better), including only the part specific for this icon.

When ever the full devicon.json is needed for build or publish it could be merged with a tool like jq or similar,
by iterating over all icon folders, and therefore automatically produce the alphabetical order we want.

Context

I think the pro side of this split up is, that the contributors, don't need to have to remember that the alphabetical order is needed.

Possible Solution

No response

Additional information

No response

[Yash]

then what about the devicon.json that are using now?

[Patrik Wehrli]

then what about the devicon.json that are using now?

in a inital step, we would need to split the current single devicon.json into multiple parts, and add them to the icon folders.

[Yash]

Should I work on this issue?

[Patrik Wehrli]

i think this needs more input from the project team, specially the people who are familiar with the build / publish part.
so currently this is more a idea/discussion thing. and not (yet) ready for some implementation.