You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of the EnumGenerator<T> does not inspect the enum for the [Flags] attribute to determine if the enum values should be generated as a collection of values bitwise or'd together or as a set of individual and distinct values. It should. Additionally, the decision to use flags or non-flags behavior should be able to be overridden based upon a value in the constructor (something akin to bool useFlags).
Task
Add first class support for [Flags] enums in EnumGenerator<T>. By default, enums with the [Flags] attribute should be generating values with one or more values or'd together, and those lacking the attribute should do the current behavior. However, this can and should be able to be overridden on an enum-by-enum basis in the constructor.
The text was updated successfully, but these errors were encountered:
Background
The current implementation of the
EnumGenerator<T>
does not inspect the enum for the[Flags]
attribute to determine if the enum values should be generated as a collection of values bitwise or'd together or as a set of individual and distinct values. It should. Additionally, the decision to use flags or non-flags behavior should be able to be overridden based upon a value in the constructor (something akin tobool useFlags
).Task
Add first class support for
[Flags]
enums inEnumGenerator<T>
. By default, enums with the[Flags]
attribute should be generating values with one or more values or'd together, and those lacking the attribute should do the current behavior. However, this can and should be able to be overridden on an enum-by-enum basis in the constructor.The text was updated successfully, but these errors were encountered: