Add 71 new File icons and create new opacity preference

[iggy890]

Description

This PR adds 71 new file icons FileIcon.swift, this PR is a draft and file icons are being added.

Related Issue

Closes #1115

• ✨ Icons for every file format and file format opacity #1115

Checklist

• I read and understood the contributing guide as well as the code of conduct
• My changes generate no new warnings
• My code builds and runs on my machine
• I documented my code
• Review requested

Screenshots

I cannot add all the file icons but here are 3:

[lukepistrol]

Needs #1113 to be merged first

[matthijseikelenboom]

The way this is written, is this even extendable? I don't see how extension developers can build upon this

[iggy890]

The way this is written, is this even extendable? I don't see how extension developers can build upon this

It’s not hard to extend at all, in fact it’s quite easy.

[matthijseikelenboom]

You do know that they cannot add an extra enum case right? As an extension developer, you don't have access to the implementation code of CodeEdit

[iggy890]

You do know that they cannot add an extra enum case right? As an extension developer, you don't have access to the implementation code of CodeEdit

Didn’t know that, thanks for alerting me I’ll create a function to add extra enum cases.

[iggy890]

You do know that they cannot add an extra enum case right? As an extension developer, you don't have access to the implementation code of CodeEdit

Unfortunately you cannot add a new case to an enum: https://stackoverflow.com/questions/53113895/how-to-add-more-cases-for-enum-in-swift

[lukepistrol]

You do know that they cannot add an extra enum case right? As an extension developer, you don't have access to the implementation code of CodeEdit

Unfortunately you cannot add a new case to an enum: https://stackoverflow.com/questions/53113895/how-to-add-more-cases-for-enum-in-swift

That's what @matthijseikelenboom was talking about 😉

[iggy890]

You do know that they cannot add an extra enum case right? As an extension developer, you don't have access to the implementation code of CodeEdit

Unfortunately you cannot add a new case to an enum: https://stackoverflow.com/questions/53113895/how-to-add-more-cases-for-enum-in-swift

That's what @matthijseikelenboom was talking about 😉

Whoops, maybe I can resolve that in a future PR and for now create and issue

[matthijseikelenboom]

@iggy890 What issue are you going to create? What would it be about?

[iggy890]

@matthijseikelenboom It would be called "Icon extendability", I'll create right now.

[matthijseikelenboom]

@iggy890 No no, just leave it for now

[iggy890]

@matthijseikelenboom Alright. ✅

[iggy890]

@lukepistrol Can this PR be changed to an active PR, I suspect the blocking tag is well, blocking it.

[austincondiff]

The 'blocking' label is there for a reason. This PR hardcodes these icons in place. @lukepistrol and @matthijseikelenboom are trying to tell you that we want these icons bundled in an icon set separate from SF Symbols so that developers writing extensions for CodeEdit can create their own icon sets to use in place of the default one we would create. This PR does not align with this goal and would have been thrown out if it were merged. I am closing this PR.

Edit: @lukepistrol @matthijseikelenboom is this something we want to get us by until that point? If so feel free to reopen.