relequestual / json-schema-dev Goto Github PK

See if https://playwright.dev might be a good solution.
Consider https://testing-library.com/docs/vue-testing-library/intro/
For reference https://timdeschryver.dev/blog/generated-tests-with-xstate-and-cypress

There is a lot of "dead" space in the current design. The "active" parts of the UI could be rearranged to make better use of the user's available screen space.

A significant amount of logic and layout for the app is currently in App.vue. This is fine for an MVP, but before adding more complexity it would be helpful to decompose the application into a number of smaller, easier to understand, easier to edit parts.

Tapping in the "share" textbox selects the text automatically on desktop, but not on mobile (or at least not on iOS). For consistency of UX, it should work across all platforms.

I wanted to check idn-email format but it looks like using of ajv-formats-draft2019 package is missing.

Currently the editor windows are a fixed size. It would be useful if it were possible to toggle between showing both the schema and instance, just the schema, or just the instance. This feature is common on online editors such as CodeSandbox, JSBin, JSFiddle, etc.

Maybe put another cross / tick on the json instance side?

I think it'd be cool if this site could be set up with a lib selector which would allow testing the same schema with different libraries.

I'd be happy to set up a server that could be called to perform validations using JsonSchema.Net.

It would need a disclaimer that says client-side validation isn't supported for this and probably other libs.

Alternative to calling a server (for .Net at least)

iOS will "zoom" the page in when selecting an <input /> or <textarea /> with a font size less than 16. This "breaks" the layout and leads to a suboptimal experience. Also, small font sizes are hard to read for many users, so it's not the best UX anyway.

Auto complete based on the default schema OR based on a custom schema if $schema is provided and it is network addressable.

User request:
https://stackoverflow.com/questions/58107229

Currently, if a $ref is unresolveable, the error is not reported to the end user and results in an uncaught error.

Example:

{
  "type": "object",
  "$ref": "foo.json"
}

Rather than using the query parameter (?shareData=abcdef) for share links, use a URL segment (/s/abcdef). This is slightly shorter and slightly neater.

Catch and handle unknown formats

This ensures that GitHub promotes them to contributors: https://help.github.com/en/articles/setting-guidelines-for-repository-contributors