You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @RitoG09 , I'm not sure to be honest. Could also be a bit more subtle like how we promote the linter here. I'd need to think about it. Any ideas?
You are welcome to give it a shot yourself, however keep in mind that we probably don't want to promote yet. We want the extension to reach a v1 and probably get to be verified by Microsoft as a publisher on the store. Might take a while!
@jviotti makes sense, thank you for the clarification.
I had another thought and wanted to share it with you
On pages like https://www.learnjsonschema.com/2020-12/applicator/properties/ , there’s already an Examples section
with sample schemas. A very subtle option could be a short line below each example, framed as “try this locally”, e.g. suggesting that users can copy the schema into their editor and use the extension to visualize, lint, or validate it.
That is an interesting idea. I know there are online versions of VS Code. I wonder if there is a way that you could truly open VS Code in your browser with the content of the schema and the extension running. That'd be killer
I took a look at the extension from vscode web perspective. vscode web runs extensions in a sandboxed browser host, so supporting it would require separating the core logic from Node APIs, making the validation/linting layer browser safe (pure JS or WASM)
As of now we can only render a button which redirects to the sourcemeta studio extension marketplace (https://marketplace.visualstudio.com/items?itemName=sourcemeta.sourcemeta-studio)
So do you think it’s worth spending time making the extension web-compatible at this stage, or is it better treated as a longer term goal after v1 and microsoft verification?
Activity
RitoG09 commentedon Dec 23, 2025
@jviotti , Can you describe it more how can we promote in learnjsonschema.com. Should it be done like JSON Schema CLI?
can you assign me the issue to work on?
jviotti commentedon Dec 23, 2025
Hey @RitoG09 , I'm not sure to be honest. Could also be a bit more subtle like how we promote the linter here. I'd need to think about it. Any ideas?
You are welcome to give it a shot yourself, however keep in mind that we probably don't want to promote yet. We want the extension to reach a v1 and probably get to be verified by Microsoft as a publisher on the store. Might take a while!
RitoG09 commentedon Dec 24, 2025
@jviotti makes sense, thank you for the clarification.
I had another thought and wanted to share it with you
On pages like https://www.learnjsonschema.com/2020-12/applicator/properties/ , there’s already an Examples section
with sample schemas. A very subtle option could be a short line below each example, framed as “try this locally”, e.g. suggesting that users can copy the schema into their editor and use the extension to visualize, lint, or validate it.
jviotti commentedon Dec 24, 2025
That is an interesting idea. I know there are online versions of VS Code. I wonder if there is a way that you could truly open VS Code in your browser with the content of the schema and the extension running. That'd be killer
RitoG09 commentedon Dec 24, 2025
I took a look at the extension from vscode web perspective. vscode web runs extensions in a sandboxed browser host, so supporting it would require separating the core logic from Node APIs, making the validation/linting layer browser safe (pure JS or WASM)
As of now we can only render a button which redirects to the sourcemeta studio extension marketplace (https://marketplace.visualstudio.com/items?itemName=sourcemeta.sourcemeta-studio)
So do you think it’s worth spending time making the extension web-compatible at this stage, or is it better treated as a longer term goal after v1 and microsoft verification?
jviotti commentedon Dec 25, 2025
Yeah, let's wait! I guess just some basic promotion in learnjsonschema.com will do, but let's wait until we reach v1, etc!