Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change is_decodable to decodable? #132

Open
Strech opened this issue Jan 16, 2025 · 1 comment
Open

Change is_decodable to decodable? #132

Strech opened this issue Jan 16, 2025 · 1 comment
Labels
client API Anything related to the client API and its quality enhancement Improvement of existing functionality or request of improvement

Comments

@Strech
Copy link
Owner

Strech commented Jan 16, 2025

To follow the Elixir naming convention

Type checks and other boolean checks that are allowed in guard clauses are named with an is_ prefix.

Examples: Integer.is_even/1, is_list/1

These functions and macros follow the Erlang convention of an is_ prefix, instead of a trailing question mark, precisely to indicate that they are allowed in guard clauses.

Note that type checks that are not valid in guard clauses do not follow this convention. For example: Keyword.keyword?/1.

@Strech Strech added enhancement Improvement of existing functionality or request of improvement client API Anything related to the client API and its quality labels Jan 16, 2025
@azeemchauhan
Copy link
Contributor

@Strech I had free time, so addressed this enhancement in the PR #138

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client API Anything related to the client API and its quality enhancement Improvement of existing functionality or request of improvement
Projects
None yet
Development

No branches or pull requests

2 participants