properties_path_matches

Same shape as the *_equals variants, but the asserted value is a regex matched against string values. Non-string matches produce a clear “value is not a string” violation.

Options

Option	Type	Required	Default	Description
`if_present`	boolean		`false`	When true, a query returning zero matches is silently OK - only real matches that fail the op produce violations.
`matches`	string	yes		Rust-regex pattern to match against the value at `path`.
`path`	string	yes		`JSONPath` expression rooted at `$`.

Plus the common paths, level, id, and when fields. This table is generated from the JSON Schema; option types and defaults are authoritative.

Example

A .properties JDBC url on the wrong engine

The rule fires on this repository:

application.properties

spring.datasource.url=jdbc:mysql://localhost/app

With this .alint.yml:

version: 1
rules:
  - id: postgres-only
    kind: properties_path_matches
    paths: "application.properties"
    path: "$['spring.datasource.url']"
    matches: "^jdbc:postgresql:"
    level: error

alint check reports:

--- application.properties -----------------------------------------------------
  x  error    postgres-only
              value at path "jdbc:mysql://localhost/app" does not match regex
              ^jdbc:postgresql:

Summary (1 violation):
  x 1 error
  0 passing * 1 failing

A .properties JDBC url on postgres

This repository is compliant:

application.properties

spring.datasource.url=jdbc:postgresql://localhost/app