The extension does not run on real-time, but on file save

[jeremyfiel]

doesn't catch invalid $schema uri
doesn't catch invalid type
no metaschema warnings for sibling test with properties

doesn't seem to be updating in real time, should it?

version 0.0.2

[Karan-Palan]

Could not reproduce the issue:

[jviotti]

@jeremyfiel Did you save the file? Right now the extension triggers only on save events, and I wonder if that's it? If so, maybe worth at least adding some messaging to the extension if we detect the file has unsaved changes, maybe saying "save your changes to get a report", etc

[jviotti]

I updated the issue title. @Karan-Palan can you investigate if there is a way to make it run on real-time? For example:

• Maybe VS Code keeps unsaved changed on a temporary file location which we can use as the input

@jeremyfiel also mentioned that the Redocly extension seems to be able to do this, and it might also be executing the Redocly CLI like us. Maybe worth digging on what they do

[jeremyfiel]

not sure how helpful this may be.. from google ai

import * as vscode from 'vscode';
import { spawn } from 'child_process';
import * as path from 'path';

export function activate(context: vscode.ExtensionContext) {
    let disposable = vscode.commands.registerCommand('my-extension.runCppBinary', () => {
        // Determine the path to your bundled C++ binary
        const binaryPath = path.join(context.extensionPath, 'path', 'to', 'your', 'cpp_binary');

        // Spawn the C++ process
        const cppProcess = spawn(binaryPath);

        // Handle real-time output from the C++ binary
        cppProcess.stdout.on('data', (data) => {
            vscode.window.showInformationMessage(`C++ Output: ${data}`);
            // You can process the data and update the UI in real time here
        });

        // Handle errors
        cppProcess.stderr.on('data', (data) => {
            console.error(`C++ Error: ${data}`);
        });

        // Handle process exit
        cppProcess.on('close', (code) => {
            console.log(`C++ process exited with code ${code}`);
        });

        // Example of sending input to the C++ binary (if needed)
        // cppProcess.stdin.write('Some input\n');
    });

    context.subscriptions.push(disposable);
}

This approach allows you to separate performance-critical computations into a compiled C++ binary while using the standard VS Code Extension API for integration and user interaction. For more complex integration, consider using native Node.js add-ons, which link C++ code directly into the Node.js runtime, though this is significantly more complex to manage and build across different platforms.

---

confirmed with Redocly they use the npm package directly in the extensions, not the cli, directly.

[jviotti]

I think the key here is to update the CLI to take schemas on standard input. Then we can pipe and never need to bother with files. I'll make an issue on the CLI