When using TNeonConfiguration.SetEnumAsInt(True), custom attribute [NeonEnumNames] is ignored. This prevents field-level control over enum serialization — making it impossible to serialize some fields as strings and others as integers within the same class.
This behavior limits flexibility and makes attributes like [NeonEnumNames] ineffective when SetEnumAsInt(True) is active. Would it be possible for Neon to prioritize field-level attributes over global configuration, allowing more granular control?
Thanks!
When using TNeonConfiguration.SetEnumAsInt(True), custom attribute [NeonEnumNames] is ignored. This prevents field-level control over enum serialization — making it impossible to serialize some fields as strings and others as integers within the same class.
This behavior limits flexibility and makes attributes like [NeonEnumNames] ineffective when SetEnumAsInt(True) is active. Would it be possible for Neon to prioritize field-level attributes over global configuration, allowing more granular control?
Thanks!