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
Right now, we are only allowing pre-set values for configurations. An example is the Lifetime enum which only has options for the values .low, medium, and .high.
The advantage that brings is that developers do not need to know about the internals happening and the values that are being set for each of the cases.
The disadvantage is that it limits creativity and customization options.
We want to strike a sweet balance here and therefore suggest adding a .custom(CGFloat) option, making use of associated values for enums. Therefore developers not caring about the internals can still use the existing cases while more avid users can dive deep into customization with the .config option.
The text was updated successfully, but these errors were encountered:
Right now, we are only allowing pre-set values for configurations. An example is the
Lifetime
enum which only has options for the values.low
,medium
, and.high
.The advantage that brings is that developers do not need to know about the internals happening and the values that are being set for each of the cases.
The disadvantage is that it limits creativity and customization options.
We want to strike a sweet balance here and therefore suggest adding a
.custom(CGFloat)
option, making use of associated values for enums. Therefore developers not caring about the internals can still use the existing cases while more avid users can dive deep into customization with the.config
option.The text was updated successfully, but these errors were encountered: