Skip to content

Made small change to the extention so that an autoit icon will appear… - #255

Open
enthusedcoder wants to merge 1 commit into
loganch:masterfrom
enthusedcoder:explorer_icon_set
Open

enthusedcoder wants to merge 1 commit into
loganch:masterfrom
enthusedcoder:explorer_icon_set

Conversation

@enthusedcoder

Copy link
Copy Markdown

Description

This is more of an aesthetic fix than a functional one. Right now, when you look at AutoIT (.au3) files in vscode's explorer, there is no icon that displays next to it, making it look like a general file:

image

I figured that I would make a small change so that AutoIT files would display an actual AutoIT icon next to them in the explorer, kind of like this:

image

🔗 Linked GitHub Issues

Closes #<number>

📋 What is the current behavior?

No icon next to Autoit files in vscode explorer.

🚀 What is the new behavior?

AutoIT icon displayed next to AutoIt files in vscode explorer


Type of changes

  • 🪲 Bugfix (change which fixes an issue)
  • ⭐ New Feature (change which adds functionality)
  • 🔒 Security fix (change which improves security)
  • 🔮 Code style update (formatting, renaming)
  • 🔨 Refactoring (code optimization without functional change)
  • 📚 Documentation (updates to README or docs)
  • ⚙️ Build or CI related changes
  • [x ] 🧿 Other type

Breaking changes 🔥

  • Yes
  • [x ] No

How and where was this tested?

🖥️ Describe where you tested your changes

System:

  • [x ] Windows 11 (x64)
  • [x ] Windows 10 (x64)
  • Windows 10 (x86)
  • other Windows version
  • other operating system

Context:

  • in Browser <name and version>
  • with Go <version>
  • with Node.js <version>
  • with AutoIt <version>
  • with .NET (C#) <version>
  • with ...

🔬 Describe how you tested your changes

  • Manually tested in system and context shown above
  • Ran automatic tests (unit tests, integration tests, etc.)
  • Other ways

Checklist

  • I have read and understood the available contributing guidelines.
  • I have ensured my code follows the available code conventions.
  • I have reviewed my changes.
  • I have made corresponding changes to the documentation (if applicable).
  • I have added/updated necessary tests to cover the changes (if applicable).
  • I have checked for potential security implications.

Additional context

Screenshots

Note to reviewers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant