wol-soft / php-json-schema-model-generator-production / 29520360842

45%

master: 46%

Build Type

Pull #19

github

Committed by claude

Commit Message

Add a data-instance JSON pointer to ValidationException

Addresses the "full property path" request from issue #131: alongside the
existing getJsonPointer() (which points into the schema), every
ValidationException now exposes getInstancePointer() — an RFC 6901 pointer
into the data that was validated (e.g. "/goals/0/kind").

Resolution is lazy, via a parent-chain set up by setInstancePointerParent():
each wrapping exception (InvalidItemException, InvalidTupleException,
InvalidAdditionalPropertiesException, InvalidPatternPropertiesException,
NestedObjectException, InvalidComposedValueException, ConditionalException)
links the exceptions it collects to itself as exceptions bubble up from the
point of failure to the root. Resolving lazily (rather than eagerly
concatenating strings at each level) is what makes arbitrarily deep nesting
work correctly — composition inside an array item inside another array, for
example — since a wrapper added after a child was constructed is still
picked up when the pointer is finally read.

Two wrinkles handled along the way:
- Composition/conditional branches validate the same value at the same
  position as their parent, so they link to it without replacing their own
  segment (they contribute nothing themselves); array/tuple items and
  additional/pattern properties instead replace their child's segment,
  since those children were constructed with a placeholder propertyName
  shared by every instance of the collection.
- InvalidAdditionalPropertiesException and InvalidPatternPropertiesException
  themselves run as base validators with no access to the property name
  their parent used to reach them, so they fall back to the generated class
  name for message text only; that placeholder is suppressed from their own
  instance pointer segment so it doesn't leak into the resolved path.

Pull Request Pull Request #19: Re-indent nested composition/conditional messages under their own bullet

Coverage Stats

57 of 59 new or added lines in 8 files covered. (96.61%)

1 existing line in 1 file now uncovered.

361 of 829 relevant lines covered (43.55%)

1.38 hits per line