Replies: 1 comment
-
@kraabrsg this section in the docs gives guidance and examples for property groups. When you use backslashes you always need to type two to escape it or the editor will even show you a red squiggle as you are creating an invalid string in your json. Forward-slashes you type a single one. However, we recommend using a path relative to your workspace and not an absolute path. That would also make sharing property groups with others easier. Also enable debug level logging to trace why your includes fail. For example, I added this property group in our sample repo "zopeneditor.propertygroups": [
{
"name": "PL1-absolute",
"type": "local",
"language": "pl1",
"syslib": [
"C:\\Users\\peter\\Dev\\wazi-sample\\INCLUDES"
]
},
{... Then I can see log entries such as these. You can double click the request id (6sgztn in my case) in the VS Code log viewer to have the editor highlight all the other relevant occurrences in the log related to that request and scroll down:
The log file shows you all the property groups that it is considering, the folders it is searching in and where it found the file. If it cannot find it then it will show that with this message:
If you have remote property groups it will show you errors of trying to receive them, which could be a no-found or if there are problems with your Zowe profile respective other messages coming back from RSE API or z/OSMF. If it does not find it in the end it will log a WARN level message.
Hope this helps giving you some pointers for how to analyze it. |
Beta Was this translation helpful? Give feedback.
-
Hi there,
we made tasks with powershell to automate project setup in vscodium.
To set a project and download the necessary files to a folder just writing in "product" and "release" is needed.
This means also each time all files are downloaded to a local folder.
To somehow avoid that only changed files should be downloaded from the mainframe.
We can't manage to successfully resolve local copybooks (a *.code-workspace file is used to resolve the mainframe files )
"zopeneditor.propertygroups": [ { "name": "mvs-members", "type": "mvs", "syslib": [ "zzzz.ttt.xxxx", "xxxx.yyyy.zzz", ] }
i have tried this example(in the folder i have files with xxxxx.INC like set in "zopeneditor.datasets.pl1Datasets" ) from
https://ibm.github.io/zopeneditor-about/Docs/setting_propertygroup.html#_3-absolute-path-patterns :
"name": "local-files", "type": "local", "syslib": [ "C:\Users\\Desktop\zopeneditor-sample\COPYBOOK", "C:/Users//Desktop/zopeneditor-sample/INCLUDES" ],
When opening a pl1 file just copybooks from type MVS get resolved but no local files.
Am i missing something (z open editor version 1.2.1)?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions