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
zserio generated HTML docs contain enum values also for auto-generated/implicitly assigned enum values. This is misleading and can be confusing when talking about the enum values, because it creates the impression that schema authors have explicitly decided to assign value. But exactly the opposite is the case, schema authors use this feature with "I don't care about the actual value, but assume that zserio keeps it stable as long as the position of the element doesn't change" in mind.
Example:
enumuint8Colors
{
RED,
GREEN,
BLUE
};
Generate the HTML docu and the result will contain RED = 0, GREEN = 1 and BLUE = 2 as if the author did that explicitly.
Suggestion: Omit these values in this case, the author intended that users should not care about the actual value when studying the schema.
In case there are users who really need the value the explicit assignment could be commented `// = 1, assigned implicitly'
The text was updated successfully, but these errors were encountered:
zserio generated HTML docs contain enum values also for auto-generated/implicitly assigned enum values. This is misleading and can be confusing when talking about the enum values, because it creates the impression that schema authors have explicitly decided to assign value. But exactly the opposite is the case, schema authors use this feature with "I don't care about the actual value, but assume that zserio keeps it stable as long as the position of the element doesn't change" in mind.
Example:
Generate the HTML docu and the result will contain
RED = 0, GREEN = 1 and BLUE = 2
as if the author did that explicitly.Suggestion: Omit these values in this case, the author intended that users should not care about the actual value when studying the schema.
In case there are users who really need the value the explicit assignment could be commented `// = 1, assigned implicitly'
The text was updated successfully, but these errors were encountered: