godotengine / godotengine/godot

[Editor] Disabling `JSON` Feature Stops `.json` Files from Showing in the FileSystem

Open
#98,227 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion topic:editor
Dominant language
C++
Stars
117k
Forks
26.8k
PR merge metrics
PR metrics pending

Description

Tested versions

v4.3.stable.official [77dcf97d8] & latest master

System information

Godot v4.4.dev.mono (af77100e3) - Windows 10.0.17763 - Multi-window, 4 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Ti (NVIDIA; 32.0.15.6109) - AMD Ryzen 9 5900X 12-Core Processor (24 threads)

Issue description

When the JSON feature is turned off in Editor/Managed Editor Feature Profiles windows, Godot Editor also stops showing the *.json files in FileSystemDock, even if the json extension is set from the EditorSettings/Docks/FileSystem/TextFile Extensions.
Such behavior should be documented if intended.
Or, when the JSON feature is off, the JSON file should be imported as plain text files (as opposed to Resource).

Steps to reproduce
  1. Create a new Project
  2. Create a JSON file in the FileSystem
  3. Goto Editor/Managed Editor Feature Profiles and disable the JSON feature

https://github.com/user-attachments/assets/97e2929b-82b5-4163-b6ff-687c7cbdedf2

Minimal reproduction project (MRP)

N/A

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

Reproduce the behavior through Editor/Managed Editor Feature Profiles and inspect how FileSystemDock handles the JSON feature and the EditorSettings/Docks/FileSystem/TextFile Extensions setting. Done means determining whether the behavior is intended and documenting it, or keeping .json files visible as plain text when JSON is disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.