[michaelstaib]

With EnableFlagEnums turned on, a flags enum input where every flag is false fails with "Flags need to have at least one selection". This means a client cannot set a flags value to zero. It also means a zero value the API returns cannot be sent back, because the output shows zero as an object with every flag false.

The input now treats an explicit false as a selection, so an object with no flag set to true and at least one flag set to false becomes 0. An empty object {} and an object where every field is null still fail with the same error as before.

# before: error "Flags need to have at least one selection"
# after: the resolver receives ExpenseTypes 0
mutation {
  updateExpense(types: { isParking: false, isTolls: false }) {
    isParking
    isTolls
  }
}

[github-actions]

Patch coverage

100.0% of changed lines covered (4/4)

File	Covered	Changed	Patch %
…/Core/src/Types/Types/Interceptors/FlagEnumTypeInterceptor.cs	4	4	100.0% 🟢

---

Project coverage: 59.5% (317675/534260 lines)