ZCodeScan ZAPP schema reports false-positive error for valid baselines property

[yukinoba]

Development environment used

• Z Open Editor version: 6.6.0
• Editor Platform: ✅ Visual Studio Code (Bob)
• Editor Platform Version: 1.121.0 (Bob 2.0.1)
• Operating System: Windows 10 Build 26200 (with WSL Ubuntu 24.04.4 LTS)
• Java Version: Not installed / not applicable
• Node.js version: 18.19.1
• Related to RSE API? No
• Logs attached: No

---

Problem Description

The built-in ZAPP schema bundled with Z Open Editor reports a schema validation
error for the baselines property inside a zcodescan profile, even though
this property is documented as valid in the official IBM documentation.

Steps to reproduce

1. Open (or create) a zapp.yaml file at the workspace root.
2. Define a zcodescan profile that includes a baselines entry, for example:

profiles:
  - name: zcodescan
    type: zcodescan
    settings:
      rules:
        - type: local
          locations:
            - "zcodescan/sam-rules.yaml"
      customRuleModels:
        - type: local
          locations:
            - "zcodescan/rules-domains.yaml"
      baselines:
        - type: local
          locations:
            - "zcodescan/baseline.json"

3. Observe the red squiggly underline on the baselines key and the
   following diagnostic in the Problems panel:

[yaml-schema: ZCodeScan profile] Property baselines is not allowed. (513)

Observed behavior

The YAML schema validation (provided by the Red Hat YAML extension using the
ZAPP schema bundled inside Z Open Editor) marks baselines as an
unrecognised / disallowed property and produces error code 513.

Expected behavior

No validation error should be raised. The baselines property is explicitly
listed as a valid setting for a zcodescan ZAPP profile in the official
IBM documentation:

Code analysis with IBM ZCodeScan
https://www.ibm.com/docs/en/developer-for-zos/17.0.x?topic=eclipse-code-analysis-zcodescan

The full profile structure documented there includes:

profiles:
  - name: zcodescan
    type: zcodescan
    settings:
      rules: [...]
      customRuleModels: [...]
      customRuleJars: [...]
      baselines:          # ← documented as valid
        - type: local
          locations:
            - "zcodescan/baseline.json"

Root cause hypothesis

The ZAPP JSON schema bundled with Z Open Editor version 6.6.02 appears to be
missing the baselines property definition for the ZCodeScan profile
settings object. The schema needs to be updated to include baselines (with
the same type / locations sub-structure used by rules and
customRuleModels) so that it matches the documented feature set.

Additional context

• The sample project zopeneditor-sample-wazi-demo ships a zcodescan/baseline.json
  file and references it via baselines in zapp.yaml, so this false-positive
  affects users of the official IBM sample repository out of the box.
• rules and customRuleModels use an identical sub-structure and are
  accepted without error — only baselines triggers the warning.

[yukinoba]

Additional verification:

After adding workspace settings for the missing ZAPP variables, the variable warnings disappeared, but the baselines schema error still remains after Developer: Reload Window.

I also explicitly configured:

• zopeneditor.zapp.customZappSchemaLocation
• yaml.schemas for **/zapp.yaml

to point to the local bundled schema:

C:\Users\NicholasChien\.bobide\extensions\ibm.zopeneditor-6.6.0-universal\resources\zapp-schema-1.10.0.json

However, the diagnostic still reports:

Property baselines is not allowed. yaml-schema: ZCodeScan profile (513)

I inspected the local bundled zapp-schema-1.10.0.json, and ZCodeScanSettings does contain baselines, along with rules, customRuleModels, and customRuleJars. The embedded schema content in dist/extension.js also appears to contain baselines.

So the issue may not be that the bundled schema file is missing baselines; it may be that the YAML language server / Z Open Editor schema registration path is applying a stale or different ZCodeScan profile schema fragment that does not include baselines, or that a cached schema association is taking precedence.

[phaumer]

Yes, check the the status bar if the yaml editor complains about conflicting schema for zapp. Also check the hovers with ZAPP tool tips that they list the correct schema version 1.10.0. Then check all your settings files: user, workspace, folder, remote: if there are "yaml.schemas": { entires that list to older versions. Just clear them our an restart the editor to repopulate them again with that latest version. Normally our activation code checks for these and swaps out old versions against the latest.