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
One thing that confused me at the beginning was that builders start with lower case (e.g. ifStatement) and types start with upper case (i.e. IfStatement).
Is there a particular reason for this? Or maybe this feels more intuitive for others (I don't find it intuitive). Would it be possible and/or reasonable to unify them (preferable upper case to match the AST node type name)?
(if not, tools that use ast-types could always provide their own unified API I guess)
The text was updated successfully, but these errors were encountered:
It's all programmatically generated, so I wouldn't mind supporting both styles for builders. For what it's worth, the lower-camel-case style came from the original Mozilla Parser API.
One thing that confused me at the beginning was that builders start with lower case (e.g.
ifStatement
) and types start with upper case (i.e.IfStatement
).Is there a particular reason for this? Or maybe this feels more intuitive for others (I don't find it intuitive). Would it be possible and/or reasonable to unify them (preferable upper case to match the AST node type name)?
(if not, tools that use ast-types could always provide their own unified API I guess)
The text was updated successfully, but these errors were encountered: