Fix file duplication issue - YAML validator now skips JSON files when not in yamlAsJson mode

[Copilot]

Problem

When using the files input to specify both JSON and YAML files, the action was processing files twice and reporting incorrect file counts. For example:

files: |
  moonstone-configuration.json
  manifests-configuration.yaml

Would produce output like:

moonstone-configuration.json is valid
moonstone-configuration.json is valid  # ❌ Duplicate processing
manifests-configuration.yaml is valid
✅ all 1 detected JSON files are valid
✅ all 2 detected YAML files are valid  # ❌ Wrong count

Root Cause

The YAML validator was missing logic to skip JSON files when yamlAsJson is false. While the JSON validator correctly skipped YAML files, the YAML validator processed all files from the files input regardless of their extension, leading to duplicate processing of JSON files.

Solution

Added symmetrical logic to the YAML validator to skip JSON files when not in yamlAsJson mode:

1. Added jsonExtension input parameter to the YAML validator
2. Added JSON file detection logic similar to how the JSON validator detects YAML files
3. Added debug logging for transparency when JSON files are skipped
4. Added test coverage to ensure the fix works correctly

After Fix

The same configuration now produces correct output:

moonstone-configuration.json is valid  # ✅ Processed by JSON validator only
manifests-configuration.yaml is valid  # ✅ Processed by YAML validator only
✅ all 1 detected JSON files are valid  # ✅ Correct count
✅ all 1 detected YAML files are valid  # ✅ Correct count

Changes Made

• src/functions/yaml-validator.js: Added logic to detect and skip JSON files when yamlAsJson is false
• tests/functions/yaml-validator.test.js: Added missing environment variable and test case for JSON file skipping

Verification

• ✅ All existing tests pass (95/95)
• ✅ 100% test coverage maintained
• ✅ New test specifically validates JSON file skipping behavior
• ✅ Code formatting and linting passes
• ✅ Changes bundled for production

Fixes #70.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• img.shields.io
  • Triggering command: node /home/REDACTED/work/json-yaml-validate/json-yaml-validate/node_modules/.bin/make-coverage-badge --output-path ./badges/coverage.svg (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.