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
What do you think about adding the ability to enforce naming for certain types?
One that comes to mind is enforcing error naming. E.g., if the attribute is an error then it must be named "error" or some user-configurable list like:
error-type-names: ["error", "secondary_error"]
The text was updated successfully, but these errors were encountered:
In slog, kinds (value types) do not treat errors as a first class citizen. Instead, you have to convert them to strings first. Did you have a potential implementation in mind for this feature?
What do you think about adding the ability to enforce naming for certain types?
One that comes to mind is enforcing error naming. E.g., if the attribute is an
error
then it must be named"error"
or some user-configurable list like:The text was updated successfully, but these errors were encountered: