@codingame/monaco-editor-wrapper 16.2.0 → 17.0.0

package/dist/assets/{broadcomMFD.cobol-language-support-2.4.0.vsix → broadcomMFD.cobol-language-support-2.4.3.vsix}/proc_grps.schema.json

@@ -25,13 +25,7 @@
               }
             ]
           },
-          "libs": {
-            "type": "array",
-            "description": "List of folders that contain copybooks.",
-            "items": {
-              "type": "string"
-            }
-          },
+          "libs": { "$ref": "libs_config.schema.json" },
           "copybook-extensions": {
             "type": "array",
             "description": "List of possible copybook file extensions.",
@@ -48,7 +42,7 @@
           }
         }
       },
-      "required": ["name"]
+      "required": ["name", "libs"]
     }
   },
   "required": ["pgroups"]

package/dist/assets/{broadcomMFD.cobol-language-support-2.4.0.vsix → broadcomMFD.cobol-language-support-2.4.3.vsix}/readme.md

@@ -2,8 +2,9 @@
 
 [![Build Status](https://github.com/eclipse-che4z/che-che4z-lsp-for-cobol/actions/workflows/build.yml/badge.svg)](https://github.com/eclipse-che4z/che-che4z-lsp-for-cobol/actions/workflows/build.yml)
 [![GitHub issues](https://img.shields.io/github/issues-raw/eclipse/che-che4z-lsp-for-cobol)](https://github.com/eclipse/che-che4z-lsp-for-cobol/issues)
-[![slack](https://img.shields.io/badge/chat-on%20Slack-blue)](https://join.slack.com/t/che4z/shared_invite/zt-22b0064vn-nBh~Fs9Fl47Prp5ItWOLWw)
+[![slack](https://img.shields.io/badge/chat-on%20Slack-blue)](https://join.slack.com/t/che4z/shared_invite/zt-37ewynplx-wCoabaIDxN6Ofm4_XBinZA)
 [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=eclipse-che4z_che-che4z-lsp-for-cobol&metric=alert_status)](https://sonarcloud.io/dashboard?id=eclipse-che4z_che-che4z-lsp-for-cobol)
+[![Code4z](https://img.shields.io/badge/Code4z-marketplace-cc092f)](https://marketplace.visualstudio.com/search?term=code4z&target=VSCode)
 
 </div>
 
@@ -15,9 +16,13 @@ COBOL Language Support recognizes files with the extensions `.cob`, `.cbl` and `
 
 This extension is a part of the Che4z open-source project. To contribute and report issues, visit our [Git repository](https://github.com/eclipse/che-che4z-lsp-for-cobol).
 
-COBOL Language Support is also part of [Code4z](https://techdocs.broadcom.com/code4z), an all-round VS Code extension package that offers a modern experience for mainframe application developers, including tools for language support, data editing, testing, and source code management. For an interactive overview of Code4z, see the [Code4z Developer Cockpit](https://mainframe.broadcom.com/code4z-developer-cockpit).
+<img align="left" alt="This extension is part of the Code4z experience" width="80" height="82" src="https://raw.githubusercontent.com/BroadcomMFD/code4z/refs/heads/main/icon5.png" />
 
-## Prerequisites
+COBOL Language Support is part of the [Code4z](https://techdocs.broadcom.com/code4z) experience from Broadcom, which offers a modern experience for mainframe application developers. To get started with Code4z, check out our foundational [extension pack](https://marketplace.visualstudio.com/items?itemName=broadcomMFD.code4z-extension-pack).
+
+<br />
+
+## Address Software Requirements
 
 There are no client or server-side prerequisites for COBOL Language Support.
 
@@ -39,7 +44,7 @@ Integrating COBOL Language Support with the Zowe Explorer and Explorer for Endev
 
 Both Zowe Explorer and Explorer for Endevor are available as part of the [Code4z extension pack](https://marketplace.visualstudio.com/items?itemName=broadcomMFD.code4z-extension-pack). A Zowe Explorer `zosmf` or `zftp` profile with credentials and a connection URL is also required to retrieve copybooks from mainframe data sets.
 
-<a href="https://www.openmainframeproject.org/all-projects/zowe/conformance"><img alt="This extension is Zowe v2 conformant" src="https://artwork.openmainframeproject.org/other/zowe-conformant/zowev2/explorer/color/zowe-conformant-zowev2-explorer-color.png" width=20% height=20% /></a>
+<a href="https://www.openmainframeproject.org/all-projects/zowe/conformance"><img alt="This extension is Zowe v3 conformant" src="https://artwork.openmainframeproject.org/other/zowe-conformant/zowev3/explorer-vs-code/color/zowe-conformant-zowev3-explorer-vs-code-color.png" width=20% height=20% /></a>
 
 ## Features
 COBOL Language Support provides the following COBOL syntax awareness features:
@@ -57,14 +62,14 @@ Autocomplete speeds up the coding process by intuitively suggesting the most lik
 
 The autocomplete feature is only available in the main COBOL file, not in copybooks.
 
-![Autocomplete](https://github.com/eclipse/che-che4z-lsp-for-cobol/raw/HEAD/docs/images/CLSAutocorrect.gif)
+![Autocomplete](https://raw.githubusercontent.com/eclipse-che4z/che-che4z-lsp-for-cobol/cb6b4a215f285229b6c4135f46d933095c0b9dfe/docs/images/autocomplete3.gif)
 
 ### Syntax and Semantic Check for Code
 This feature checks for mistakes and errors in COBOL code. The syntax check feature reviews the whole content of the code and suggests fixes, and the semantic analysis highlights incorrect names of variables, copybooks and paragraphs.
 
 This feature is also enabled for Datacom, CICS, and DB2 SQL keywords and variables.
 
-![Syntax check](https://github.com/eclipse/che-che4z-lsp-for-cobol/raw/HEAD/docs/images/CLSErrorHighlighting.gif)
+To disable the semantic check feature, open the COBOL Language Support extension settings and change **Analysis mode** to **BASIC**.
 
 ### Syntax Highlighting
 The extension enables syntax highlighting for COBOL code.
@@ -79,10 +84,10 @@ The extension enables outline view and the breadcrumbs navigation bar at the top
 Before you write your COBOL code from scratch, search the snippet library for useful templates.
 
 1. Press **F1** to open the command palette.
-2. Type **Insert Snippet** and press enter.
+2. Run the command **Snippets: Insert COBOL Snippet**.
 3. Select the snippet that you want to insert.
 
-![Code snippets](https://github.com/eclipse/che-che4z-lsp-for-cobol/raw/HEAD/docs/images/Snippet.gif)
+![Code snippets](https://raw.githubusercontent.com/eclipse-che4z/che-che4z-lsp-for-cobol/cb6b4a215f285229b6c4135f46d933095c0b9dfe/docs/images/Snippet.gif)
 
 You can also insert a code snippet by typing the name of the snippet in your code and clicking on the autocomplete text.
 
@@ -246,7 +251,7 @@ The Find All References and Go To Definition functionalities are extended to wor
 * **Find All References** identifies all occurrences of variables and paragraphs from copybooks in the code.
 * **Go To Definition** enables you to right-click on any variable or paragraph to reveal a definition of the element. If the definition is in a copybook, or the name of a copybook, the copybook opens.
 
-![Go To Definition in a copybook](https://github.com/eclipse/che-che4z-lsp-for-cobol/raw/HEAD/docs/images/CPYGoToDefinition.gif)
+![Go To Definition in a copybook](https://raw.githubusercontent.com/eclipse-che4z/che-che4z-lsp-for-cobol/cb6b4a215f285229b6c4135f46d933095c0b9dfe/docs/images/CPYGoToDefinition.gif)
 
 #### Other
 
@@ -256,23 +261,39 @@ The Find All References and Go To Definition functionalities are extended to wor
 
 ## Processor Groups
 
-Use processor groups to link programs with specific dialects, SQL backend settings, copybook extensions, compiler options, and local folders containing copybooks. You define processor groups in a `proc_grps.json` file and associate processor groups with programs in a `pgm_conf.json` file. Create both of these files in a `/.cobolplugin` folder in your workspace root.
+Use processor groups to link programs with specific dialects, SQL backend settings, copybook extensions, compiler options, and local and remote locations that contain copybooks. You define processor groups in a `proc_grps.json` file and associate processor groups with programs in a `pgm_conf.json` file. Create both of these files in a `/.cobolplugin` folder in your workspace root.
 
 The `proc_grps.json` file is formatted as an array of JSON elements, with one JSON per processor group. Each processor group can contain the following elements:
 
 - **"name":** (string)  
     - Specify a name for the processor group.
 - (Optional) **"libs":** (array)  
-    - Specify libraries that contain copybooks as either absolute or relative local paths. These libraries are used to search for copybooks in programs linked with this processor group, and take priority over the local copybook libraries that you specify in the extension settings.
+    - Specify local folders, mainframe data sets, USS files, and Endevor locations that contain copybooks. Specify local folders as either absolute or relative local paths. These libraries are used to search for copybooks in programs linked with this processor group, and take priority over the copybook libraries that you specify in the extension settings.
+    - Specify local folders as a string.
+    - Specify remote locations as JSON elements. Use one JSON element per remote location. Specify either the **"dataset"** or **"uss"** parameter, and optionally a **"profile"**. Use one JSON element per remote location.
+        - **"dataset":** (string)
+            - Specify the full DSN of a PDS that contains copybooks.
+        - **"uss":** (string)
+            - Specify a full USS path that contains copybooks.
+        - (Optional) **"profile":** (string)
+            - Specify the name of a Zowe profile. If you do not include this parameter, the Zowe profile specified in the extension settings is used. 
+    - Specify Endevor locations as JSON elements containing the following parameters. Use one JSON element per Endevor location.
+        - (Optional) **"profile":** (string)
+            - If you use more than one Endevor connection or inventory location, specify the name of a connection or inventory location or profile in this parameter. If you only use one Endevor connection and inventory location, you can omit this parameter.
+        - **"environment":** (string)
+        - **"stage":** (string)
+        - **"system":** (string)
+        - **"subsystem":** (string)
+        - **"type":** (string)
 - (Optional) **"copybook-extensions":** (array)  
     - Specify copybook extensions that you use for the programs linked with this processor groups. These copybook extensions take priority over extensions that you specify in the extension settings.
 - (Optional) **"compiler-options":** (array)  
     - Specify compiler directives that you want to apply to the programs linked with this processor group. Currently the following directives are supported:
         - QUALIFY(*EXTEND|COMPAT*)
-		- XMLPARSE(*XMLSS|COMPAT*)
+        - XMLPARSE(*XMLSS|COMPAT*)
 	- For more information on COBOL compiler options, see the [IBM Enterprise COBOL documentation](https://www.ibm.com/docs/en/cobol-zos/6.3?topic=guide-enterprise-cobol-compiler-options).
 - (Optional) **"preprocessor":** (array)
-	- Specify dialect and SQL preprocessors that you want to apply to the programs linked with this processor group. See the [Preprocessors](#preprocessors) section below for further information.
+    - Specify dialect and SQL preprocessors that you want to apply to the programs linked with this processor group. See the [Preprocessors](#preprocessors) section below for further information.
 
 ### Preprocessors
 
@@ -296,7 +317,23 @@ A dialect preprocessor can be used to enable a COBOL dialect for a particular pr
 - **"name":** (string)
     - Specify the name of a dialect.
 - (Optional) **"libs":** (array)
-    - Specify libraries that contain copybooks written in the specified dialect as either absolute or relative local paths. These libraries are used to search for copybooks in programs linked with this processor group, and take priority over the local copybook libraries that you specify in the extension settings.
+    - Specify local folders, mainframe data sets, USS files, and Endevor locations that contain copybooks written in the specified dialect as either absolute or relative local paths. These libraries are used to search for copybooks in programs linked with this processor group, and take priority over the local copybook libraries that you specify in the extension settings.
+    - Specify local folders as a string.
+    - Specify remote locations as JSON elements. Use one JSON element per remote location. Specify either the **"dataset"** or **"uss"** parameter, and optionally a **"profile"**. Use one JSON element per remote location.
+        - **"dataset":** (string)
+            - Specify the full DSN of a PDS that contains copybooks.
+        - **"uss":** (string)
+            - Specify a full USS path that contains copybooks.
+        - (Optional) **"profile":** (string)
+            - Specify the name of a Zowe profile. If you do not include this parameter, the Zowe profile specified in the extension settings is used. 
+    - Specify Endevor locations as JSON elements containing the following parameters. Use one JSON element per Endevor location.
+        - (Optional) **"profile":** (string)
+            - If you use more than one Endevor connection or inventory location, specify the name of a connection or inventory location or profile in this parameter. If you only use one Endevor connection and inventory location, you can omit this parameter.
+        - **"environment":** (string)
+        - **"stage":** (string)
+        - **"system":** (string)
+        - **"subsystem":** (string)
+        - **"type":** (string)
  
 ### Program configuration file
 
@@ -318,15 +355,15 @@ Each element contains the following parameters:
 - **"pgroup":** (string)
     - Specify the name of a procecssor group that is defined in `proc_grps.json`.
    
-### Example
+### Example Processor Group Configuration
 
 Using the example `pgm_conf.json` file above, the following `proc_grps.json` example enables the following:
 
-- Copybooks from libraries LIB1 and LIB2, with the extensions ".cpy" and ".copy", are used with PROGRAM1.
+- Copybooks from local folders LIB1 and LIB2, with the extensions ".cpy" and ".copy", and from Endevor location PRD/2/SYS3/SUB4/COBCPY, are used with PROGRAM1. The Explorer for Endevor inventory location "inv1" is used to retrieve the dependencies from Endevor.
 - The QUALIFY(EXTEND) and XMLPARSE(COMPAT) compiler options are enabled for PROGRAM1.
-- The IDMS dialect is enabled for PROGRAM2, and IDMS copybooks from LIB3 and LIB4 are used with PROGRAM2.
+- The IDMS dialect is enabled for PROGRAM2, and IDMS copybooks from local folders LIB3 and LIB4 are used with PROGRAM2.
 - The DB2 SQL server is enabled for PROGRAM2. 
-- Non-IDMS copybooks from libraries LIB5 and LIB6 are used with PROGRAM2. 
+- Non-IDMS copybooks from USS path /remote/uss/folder, and mainframe data set HLQ.DSN.COBCOPY, are used with PROGRAM2. The Zowe profile "prof1" is used to download the copybooks from the mainframe data set, while the default profile in the extension settings is used to download the copybooks from the USS file.
 
 ```
 {
@@ -334,7 +371,15 @@ Using the example `pgm_conf.json` file above, the following `proc_grps.json` exa
         {
             "name": "GROUP1",
             "libs": [
-                "LIB1", "LIB2"
+                "LIB1", "LIB2",
+                       {
+                            "profile": "inv1",
+                            "environment": "PRD",
+                            "stage": "2",
+                            "system": "SYS3",
+                            "subsystem": "SUB4",
+                            "type": "COBCPY"
+                        }
             ],
             "copybook-extensions": [
                 ".cpy", ".copy"
@@ -358,8 +403,14 @@ Using the example `pgm_conf.json` file above, the following `proc_grps.json` exa
                 }
             ],
             "libs": [
-                "LIB5", "LIB6"
-                ]
+                        {
+                            "uss": "/remote/uss/folder"
+                        },
+                        {
+                            "dataset": "HLQ.DSN.COBCOPY",
+                            "profile": "prof1"
+                        }
+                ],
         }
     ]
 }
@@ -379,3 +430,30 @@ To enable troubleshooting logs for the LSP server, specify a value for the param
 These values are ordered from returning the least information ("ERROR"; errors only) to the most information ("ALL"; all details).
 
 To view troubleshooting logs, open the output panel and select **COBOL Language Support** from the drop-down menu.
+
+## Known Issues
+
+- If you do not have Java on your workstation, COBOL Language Support uses the native binary (engine.exe) to execute. If your environment does not allow engine.exe to execute, contact your system administrator to add an exception for engine.exe.
+- Double-byte character sets and the DBCS compiler option are not supported.
+
+
+## Privacy Notice
+
+The extensions for Visual Studio Code developed by Broadcom Inc., including its corporate affiliates and subsidiaries, ("Broadcom") are provided free of charge, but in order to better understand and meet its users’ needs, Broadcom may collect, use, analyze and retain anonymous users’ metadata and interaction data, (collectively, “Usage Data”) and aggregate such Usage Data with similar Usage Data of other Broadcom customers. Please find more detailed information in [License and Service Terms & Repository](https://www.broadcom.com/company/legal/licensing).
+
+This data collection uses built-in Microsoft VS Code Telemetry, which can be disabled, at your sole discretion, if you do not want to send Usage Data.
+
+The current release of COBOL Language Support collects anonymous data for the following events:
+* Activation of this VS Code extension
+* Problem interaction
+* Quick Fix
+* Invalid ZOWE credentials
+* ZOWE connection issues
+* Java version issues
+
+Each such event is logged with the following information:
+* Event time
+* Operating system and version
+* Country or region
+* Anonymous user and session ID
+* Version numbers of Microsoft VS Code and COBOL Language Support

package/dist/assets/{golang.Go-0.47.2.vsix → golang.Go-0.49.0.vsix}/README.md

@@ -10,7 +10,7 @@ provides rich language support for the
 
 ## Requirements
 
-* Visual Studio Code 1.75 or newer (or editors compatible with VS Code 1.75+ APIs)
+* Visual Studio Code 1.90 or newer (or editors compatible with VS Code 1.90+ APIs)
 * Go 1.21 or newer.
 
 ## Quick Start
@@ -33,7 +33,7 @@ extension fits your needs and enhances your development experience.
     the language server is running, and you are ready to go.
 
 <p align="center">
-<img src="https://github.com/golang/vscode-go/raw/v0.47.2/docs/images/gettingstarted.gif" width=75%>
+<img src="https://github.com/golang/vscode-go/raw/v0.49.0/docs/images/gettingstarted.gif" width=75%>
 <br/>
 <em>(Install Missing Tools)</em>
 </p>
@@ -78,7 +78,7 @@ application using VS Code Go.
 See the [full feature breakdown] for more details.
 
 <p align=center>
-<img src="https://github.com/golang/vscode-go/raw/v0.47.2/docs/images/completion-signature-help.gif" width=75%>
+<img src="https://github.com/golang/vscode-go/raw/v0.49.0/docs/images/completion-signature-help.gif" width=75%>
 <br/>
 <em>(Code completion and Signature Help)</em>
 </p>
@@ -91,7 +91,7 @@ then typing in the command name. See the
 extension.
 
 <p align=center>
-<img src="https://github.com/golang/vscode-go/raw/v0.47.2/docs/images/toggletestfile.gif" width=75%>
+<img src="https://github.com/golang/vscode-go/raw/v0.49.0/docs/images/toggletestfile.gif" width=75%>
 <br/><em>(Toggle Test File)</em></p>
 
 **⚠️ Note**: the default syntax highlighting for Go files is provided by a
@@ -223,7 +223,7 @@ conduct-related issue, please mail conduct@golang.org.
 
 ## License
 
-[MIT](https://github.com/golang/vscode-go/raw/v0.47.2/LICENSE)
+[MIT](https://github.com/golang/vscode-go/raw/v0.49.0/LICENSE)
 
 [Stack Overflow]: https://stackoverflow.com/questions/tagged/go+visual-studio-code
 [`gopls`]: https://golang.org/s/gopls