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
Imagine a CSV with a "day_of_week" column with string values like "monday", "friday", etc. If you could convert this column to an enum, you could use the help of completion to, for example, filter it.
It can be done the same way as generating data schemas:
after cell execution in the notebooks
on data schema import in gradle project
There are some design questions:
What if i don't need an enum?
What about normalization? "monday", "Monday" aren't the same thing.
In jupyter, you can normalize values however you want and get a nice enum.
In gradle project code generation happens once, in build time, so your values have to be normalized. How?
How many values in the enum is too much?
What if not all possible values are present in the column? What should happen if generated schema knows about 2 enum values, but the actual column at runtime has more?
The text was updated successfully, but these errors were encountered:
Imagine a CSV with a "day_of_week" column with string values like "monday", "friday", etc. If you could convert this column to an enum, you could use the help of completion to, for example, filter it.
It can be done the same way as generating data schemas:
There are some design questions:
What if i don't need an enum?
What about normalization? "monday", "Monday" aren't the same thing.
In jupyter, you can normalize values however you want and get a nice enum.
In gradle project code generation happens once, in build time, so your values have to be normalized. How?
How many values in the enum is too much?
What if not all possible values are present in the column? What should happen if generated schema knows about 2 enum values, but the actual column at runtime has more?
The text was updated successfully, but these errors were encountered: