Skip to content

camelCase vs snake_case inconsistency #14

@ghost

Description

node-telegram-bot-api uses snake_case where the Telegram API does, for consistency with the API. In coffea, some places (evt.raw and options in the object passed to reply()) use snake_case, while others use camelCase.

camelCase is the de facto standard for JavaScript code, however, I think it's more important to stay close to the API in places where the raw interface is exposed, which mostly includes reply() too. eslint can be configured to ignore non-compliance in these places with ["camelcase", {"properties": "never"}] (which is used by standard).

Either way, the current state is horribly inconsistent, so either snake_case should be consistently used where the Telegram API uses it, or camelCase should be used consistently across the whole library.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions