microsoft / microsoft/PowerToys

Fallback to plain text monaco editor if not supported file type found for plain text files

Open
#49,878 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs-Triage Product-Peek
Dominant language
C
Stars
139k
Forks
8.6k
PR merge metrics
PR metrics pending

Description

Description of the new feature / enhancement

I would like peek to fallback to still display plain text files even if there is no file extension or if the file extension is not in the list of supported files.

Scenario when this would be used?

For example the following files are common in typescript codebases but are not displayed:
.node-version
.npmrc

Even common files like the following:
LICENSE
git files such as the config file
Any .example files such as .env.example

Supporting information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating Peek's file-type support and Monaco editor integration, then check how files without supported extensions are handled. Update the fallback so plain-text files such as .node-version, .npmrc, LICENSE, git config, and .env.example are displayed, and verify that these examples open successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
57/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.