FortAwesome / Font-Awesome

The iconic SVG, font, and CSS toolkit
https://fontawesome.com
Other
73.46k stars 12.19k forks source link

Icon request: icon-file-json #11088

Open dustinpoissant opened 7 years ago

jalesmonteiro commented 7 years ago

+1

NickNiebling commented 5 years ago

+1

I will suggest making it match other "file" icons (from files category), and make it similar to file-code, but instead of "</>" it could be either "{;}" or "{...}".

Here is an example for inspiration (ignore the bottom "JSON" text of course): image https://www.onlinewebfonts.com/icon/442882

fredriklengstrand commented 5 years ago

+1

dolibarr95 commented 5 years ago

+1

NickNiebling commented 3 years ago

It would really be nice with this one.. I know title says "file-json", but since the "xml equivalent" is called "file-code", it could be called "file-code-alt" as an alternative. Suggested icon names:

Suggested "content" inside file icon:

BenCant commented 2 years ago

+1

NicMeadows commented 2 years ago

+1

NickNiebling commented 2 years ago

~1.300 new icons later (in multiple styles - compared to v.5) and we still don't have a "json file" icon.

There are a lot of file icons suited for export/integration - and the only missing file format I can think of (that is used "everywhere") is json.

Look at what's already there: image image image image image image

JSON is probably the most commonly used file format for code contracts and integration, followed by csv and then xml. In the future we might see a rise for protobuf - but for now json is the de facto standard in most cases.

Even Google Trends knows: image image

Why is json not a priority? I simply don't get it..

NickNiebling commented 2 years ago

Stack Overflow also shows a clear trend - JSON is very popular: image

cceuroform commented 2 years ago

+1

OscarBeiro commented 1 year ago

+1

yalimgerger commented 1 year ago

+1 for JSON. And for other common file formats such as CSV, Word etc... For what it is worth Bootstrap's free icon set has these icons.

sensibleworld commented 1 month ago

This is a quick update to let folks know that we’re refining our icon request workflow behind the scenes, and as part of that we’re going through all open requests and filing them into several new buckets to be addressed.

In this case we’re closing this issue because it’s a duplicate of or shares too much similarity with this request.

NickNiebling commented 1 month ago

js and json is not the same.

Also it seems like the js request contains multiple icon suggestions inside, but the last comment suggest the case will address 1 (single) icon in some future, which I assume must be js and not all of them.

I think it is wrong to merge requests as json will disappear - even when it got a lot of support here and even have a reasonable discussion around how you could implement it.

OscarBeiro commented 1 month ago

Agreed. This is not a duplicate. A new icon request can be created for icon-file-json, icon-file-xml, conf-file-csv as these are commonly used formats. Thanks @NickNiebling for the graph.

sensibleworld commented 1 month ago

Hey folks! Sorry about that! In the process of going through all of the open requests, we were bound to make a few errors. Re-opening.