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
{{ message }}
This repository was archived by the owner on Apr 22, 2026. It is now read-only.
Most of the APIs in the library consistently follow JavaScript naming conventions and uses camel case (parameter and method names).
However, several of the classes have a mixture of snake-case and camel-case method names. For example, DecisionsResponse has an add_marker() method and an addDecision() method. Similarly, EventList() has a has_timer_event() method and an eventById() method.
It would be nice if the public API of the library consistently used camel case for method names. For backwards compatibility, the existing snake-case function names should be kept as (deprecated) aliases.
Most of the APIs in the library consistently follow JavaScript naming conventions and uses camel case (parameter and method names).
However, several of the classes have a mixture of snake-case and camel-case method names. For example,
DecisionsResponsehas anadd_marker()method and anaddDecision()method. Similarly,EventList()has ahas_timer_event()method and aneventById()method.It would be nice if the public API of the library consistently used camel case for method names. For backwards compatibility, the existing snake-case function names should be kept as (deprecated) aliases.