Closed COBOL-Erik closed 11 months ago
@COBOL-Erik thanks for this item. We agree that this would be important to add. I moved the item to this repository in which we collect the Z Open Editor issues.
Hi,
Especially if the zapp file resides in the VS Code Workspace so in the Git repository because it is part of the Application and is therefore shared by all users who work with this Git repository.
Exactly! Thanks!
This is implemented now. Thanks!
Ok, thanks. We do not do environment variables, but you define variables as settings. Great to hear that this works for you.
That’s what I meant. We add the variable with a script 😊
I would like all mainframe developers to be able to share a zapp.yaml, with no need for changes by individual developers. But we have personal datasets for copy books, that follow naming conventions. Could it be possible to specify variables in the zapp.yaml file? For example something like {env:USERNAME} (used in other settings in VS Code)?