Open
Description
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
Metadata
Metadata
Assignees
Labels
No labels