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
Also current way not only force pushing using enum in such context, but force push enum code style. Library's enums styled like UperCamelCase in name and SCREAMING_CASE for keys. It's not suitable for every project. Even Typescript Documentation use UperCamelCase for name and case
The text was updated successfully, but these errors were encountered:
Hi there,
I agree that using enums for string props was not the best choice.
Would you like to submit a PR to update the API to support both enum and
union string types for backward compatibility?
Thanks,
Evyatar
It's a little annoying that the library forces me to use enгms in string props.
I think better way is change them to Union string type. Example
This way is more preferred in the community, for example it is advised by Matt Pocock.
Also current way not only force pushing using enum in such context, but force push enum code style. Library's enums styled like
UperCamelCase
in name andSCREAMING_CASE
for keys. It's not suitable for every project. Even Typescript Documentation useUperCamelCase
for name and caseThe text was updated successfully, but these errors were encountered: