-
Type: Improvement
-
Resolution: Won't Fix
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
4 - L (<= 1 quarter)
-
5328
-
Not Needed
A lot of SDKs are interfacing with Core by a C API where enums are passed between SDK/Core as an integer and translated into their respective enum values at the relevant layer. This means that any change to enum values in Core needs to be reflected in SDKs, which is error prone. Instead, Core should assign explicit values to the enums so that adding new values, regardless of its place in the file will be a non-breaking change. An example of this happening recently is this PR which added an enum member in the middle of the enum, thus changing the values of all members below it.