Disabling "Script Editor" editor feature causes external script editor to not auto-launch

[Anixias]

Tested versions

v4.4.dev4.mono.official [36e6207]

System information

Godot v4.4.dev4.mono - Windows 10.0.22631 - Multi-window, 2 monitors - OpenGL 3 (Compatibility) - NVIDIA GeForce RTX 4070 Ti SUPER (NVIDIA; 32.0.15.6614) - 13th Gen Intel(R) Core(TM) i9-13900K (32 threads)

Issue description

Disabling the "Script Editor" editor feature prevents Godot from launching the configured external editor.

In my case, I use C# and JetBrains Rider. If I have the Script Editor feature enabled, clicking the script icon in a scene correctly opens Rider, but if I disable the Script Editor feature, clicking the script icon no longer has any effect.

Steps to reproduce

1. Go to Editor > Manage Editor Features...
2. Under "Main Features:", disable the "Script Editor" feature
3. Try opening a C# script by clicking the script icon on a node in the scene hierarchy

Minimal reproduction project (MRP)

N/A

[eobet]

I don't know how to test that fix, but I just noticed that both the 2D and AssetLib main features show up in 4.4 dev4 even though they were properly disabled in 4.4 dev3 for me (the Script however, stayed disabled).

[AThousandShips]

You can download the latest artifacts from master or build from source

But those bugs were also reported on dev4 and were fixed after dev4

[eobet]

Thanks, however that crashes on my project so I'll stay on dev3 for now and hope that the missing context menu items I saw in dev4 are also fixed.

[Anixias]

The fix from #98988 shouldn't affect the external script editor bug I described above because it wasn't reordered in the enum in the first place. Would you like me to edit the issue to only be about that bug?

[AThousandShips]

Please do, but try to replicate the bug in a more recent version to get details, or test dev3 to confirm it doesn't occur there

[Anixias]

I was able to confirm the issue back in 4.3 stable, so it is not specific to dev4.

[AThousandShips]

I didn't quite catch what the original issue was due to the other details, this is not necessarily a bug but an aspect of this feature, disabling scripting disables scripting entirely

For context:

• Disabling Script Editor also disable the ability to create "New Scripts" from inspector #73702