Describe the bug
After launching actions setup, the default actions for PGM and CRTSRVPGM are created as global and are therefore available for all source files. This leads to running these actions on the wrong source.
To Reproduce
I just tested the action IBM i: Launch Actions Setup
The file extensions which are appropriate for this
I would expect to build SRVPGM and PGM from .bnddir source or from .ilesrvpgm and .ilepgm pseudo source
But this particular action seems to take the object name as input so would it work on anything but a .PGM or .SRVPGM object. Even in this case, would it not need the binder source to be useful?
Describe the bug After launching actions setup, the default actions for PGM and CRTSRVPGM are created as global and are therefore available for all source files. This leads to running these actions on the wrong source.
To Reproduce I just tested the action
IBM i: Launch Actions Setup
and the actions.json entry created
Here is the screen recording of the confusing result of this
https://github.com/IBM/vscode-ibmi-projectexplorer/assets/59372176/cbc4d226-3df8-42f0-9751-65c1e3bc5742
Expected behavior These actions should not appear for inappropriate file extensions
Environment:
The issue is not unique to these versions