Skip to content

Release 1.17.1

Choose a tag to compare

View all tags
@reid-spencer reid-spencer released this 30 Mar 19:39
· 31 commits to main since this release
1.17.1
56a902a

Release 1.17.1

Bug Fix: Remove false-positive field overloading warnings

Fields are fully scoped by their containing record type — a completedAt field in Reservation.CompletedData can never be confused with a completedAt field in OnlineOrder.OnlineOrderData. The previous warning treated same-named fields across different record types within the same context as potential overloading conflicts, producing noisy false positives.

This release suppresses the overloading check for fields specifically. Overloading detection remains active for all other definition kinds: types, states, enumerators, domains, contexts, entities, etc.

The T vs T? variant case (required field in a tailored state record, optional in a shared superset record) is also no longer flagged — this is correct modeling practice, not an overloading concern.

Assets 5
Loading