-
Notifications
You must be signed in to change notification settings - Fork 7
Description
My usual workflow for editing the content of preprocessor comments is to switch to the preprocessed file of the version where they become active, edit the code there (where I have full IDE support), and then copy back the final result to the original file.
It seems the //$$
auto-insertion however evaluates the surrounding conditions as if the file was part of the main project, even when editing files which are in a different project, so I constantly have to fight it because it inappropriately keeps trying to comment the lines I'm working on.
Side-note: An action to jump to the first version where a given line becomes active would be neat to have. Although potentially difficult to implement because it needs to be aware of the actual preprocessor graph and non-MC variable values to know where to jump (e.g. in my current project, for a 1.16+ line it should jump to 1.16.2-forge, but in other projects in may need to jump to 1.16.2-fabric, or 1.21-fabric if their main version 1.21.8-fabric).