Describe each custom format in JSON

The workflow opens a standard JSON configuration document from JSONBuddy. Add one object per format, using format for the identifier referenced by a JSON Schema and regex for the regular expression used by the validator.

[
              {
              "format": "my-custom-format",
              "regex": "^[a-zA-Z/]+$"
              }
              ]

Keep the expression, examples, and configuration revision together. A regular expression can describe a useful lexical rule, but it does not replace a complete data-contract test.

Save and reload the definitions

  1. Use the Open JSON validator custom formats command to open the configuration.
  2. Add or revise the format and regex strings, then save valid JSON.
  3. Use Reload JSON validator custom formats so open documents are checked with the changed definitions.
  4. Validate one matching value and one deliberately non-matching value.

The article introduced this behavior with JSONBuddy 4.6. Treat the command names, configuration location, reload scope, regular-expression engine, and edition access as product-specific.

Treat an override as an intentional contract change

Record that override explicitly because the same schema can produce a different result on a validator that uses the built-in meaning or ignores format assertions.

Verify editor assistance and validation together

Use that assistance to confirm the intended schema association, then run validation and review the actual result rather than treating a tooltip as proof.

Continue with a controlled validation path

Use the JSON validator for the solution overview, instant-validation guidance for the editing loop, or the validator Help task for a complete correction workflow.