Issues

Polymorphism configured through a resolver modifier (JsonTypeInfo.PolymorphismOptions) throws "Invalid JsonTypeInfo operation for JsonTypeInfoKind 'None'" once the factory is registered

ktsu-dev/JsonRequiredConditionally#67 · opened

on Oct 7, 2026

1

With reflection disabled by default, violations inside non-string-keyed dictionaries are silently accepted

ktsu-dev/JsonRequiredConditionally#63 · opened

on Oct 6, 2026

1

NotEmptyTests doesn't cross every payload shape with HashSet<T>, T[] and the custom-converted member as the not-empty spec requires

ktsu-dev/JsonRequiredConditionally#61 · opened

on Oct 5, 2026

1

No regression test guards eligibility memoization against the factorial blow-up the design spec measured (13 s for ten mutually-referencing types)

ktsu-dev/JsonRequiredConditionally#60 · opened

on Oct 5, 2026

1

Registering the factory makes deserialization quadratic in the size of any string-keyed dictionary under a claimed type (80k entries: 27 ms → 12.5 s)

ktsu-dev/JsonRequiredConditionally#58 · opened

on Oct 5, 2026

1

Registering the factory via [JsonConverter(typeof(JsonRequiredConditionallyConverterFactory))] on a type crashes the process with a stack overflow on read and write

ktsu-dev/JsonRequiredConditionally#56 · opened

on Sep 29, 2026

1

A holder built through a non-public [JsonConstructor] loses the path prefix on its violations and drops every violation after the first

ktsu-dev/JsonRequiredConditionally#55 · opened

on Sep 29, 2026

1

Violations inside a HashSet<T>, Queue<T>, LinkedList<T> or ISet<T> member are silently accepted, although the same payload is rejected at top level

ktsu-dev/JsonRequiredConditionally#51 · opened

on Sep 29, 2026

1

Deserializing a top-level List<T>/T[]/Dictionary<string,T> of a decorated type reports only the first violation, with no index (Tuning instead of [0].Tuning, [2].Tuning)

ktsu-dev/JsonRequiredConditionally#50 · opened

on Sep 28, 2026

1

With PropertyNameCaseInsensitive (incl. JsonSerializerDefaults.Web), a duplicated property is validated against a different occurrence than the one deserialized, so invalid payloads pass and valid ones are rejected

ktsu-dev/JsonRequiredConditionally#49 · opened

on Sep 28, 2026

1

Add a net472 test leg so the netstandard2.0/2.1 assets are actually exercised

ktsu-dev/JsonRequiredConditionally#14 · opened

on Aug 27, 2026

3

Navigation Menu

Repository navigation

Issues

Polymorphism configured through a resolver modifier (JsonTypeInfo.PolymorphismOptions) throws "Invalid JsonTypeInfo operation for JsonTypeInfoKind 'None'" once the factory is registered

With reflection disabled by default, violations inside non-string-keyed dictionaries are silently accepted

NotEmptyTests doesn't cross every payload shape with HashSet<T>, T[] and the custom-converted member as the not-empty spec requires

No regression test guards eligibility memoization against the factorial blow-up the design spec measured (13 s for ten mutually-referencing types)

Registering the factory makes deserialization quadratic in the size of any string-keyed dictionary under a claimed type (80k entries: 27 ms → 12.5 s)

Registering the factory via [JsonConverter(typeof(JsonRequiredConditionallyConverterFactory))] on a type crashes the process with a stack overflow on read and write

A holder built through a non-public [JsonConstructor] loses the path prefix on its violations and drops every violation after the first

Violations inside a HashSet<T>, Queue<T>, LinkedList<T> or ISet<T> member are silently accepted, although the same payload is rejected at top level

Deserializing a top-level List<T>/T[]/Dictionary<string,T> of a decorated type reports only the first violation, with no index (Tuning instead of [0].Tuning, [2].Tuning)

With PropertyNameCaseInsensitive (incl. JsonSerializerDefaults.Web), a duplicated property is validated against a different occurrence than the one deserialized, so invalid payloads pass and valid ones are rejected

Add a net472 test leg so the netstandard2.0/2.1 assets are actually exercised