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
I've identified an inconsistency where the exported entity nomenclature deviates from established JavaScript naming conventions.
While it's possible to implement a re-export solution with modified names to align with JavaScript project conventions, the requirement for such a workaround significantly impacts the library's usability and adoption potential.
Given the author's evident expertise in JavaScript development, I would appreciate understanding the rationale behind implementing Python-style naming conventions in this context
The text was updated successfully, but these errors were encountered:
I've identified an inconsistency where the exported entity nomenclature deviates from established JavaScript naming conventions.
While it's possible to implement a re-export solution with modified names to align with JavaScript project conventions, the requirement for such a workaround significantly impacts the library's usability and adoption potential.
Given the author's evident expertise in JavaScript development, I would appreciate understanding the rationale behind implementing Python-style naming conventions in this context
The text was updated successfully, but these errors were encountered: