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

chore: make sure all feature names are kebab case #114

Merged

Conversation

ROMemories
Copy link
Collaborator

Even though there is no official convention yet, we need consistent casing and kebab case seems to be the consensus in the community.

See the following for official conventions regarding casing: https://rust-lang.github.io/api-guidelines/naming.html#casing-conforms-to-rfc-430-c-case

Copy link
Collaborator

@kaspar030 kaspar030 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@kaspar030 kaspar030 force-pushed the chore/kebab-case-feature-names branch 2 times, most recently from ceeb2e9 to 5f714b2 Compare March 1, 2024 20:46
@kaspar030 kaspar030 enabled auto-merge March 1, 2024 20:48
Even though there is no official convention yet, we need consistent
casing and kebab case seems to be the consensus in the community.

See the following for official conventions regarding casing:
https://rust-lang.github.io/api-guidelines/naming.html#casing-conforms-to-rfc-430-c-case
@kaspar030 kaspar030 force-pushed the chore/kebab-case-feature-names branch from 5f714b2 to b48d2a3 Compare March 1, 2024 20:58
@kaspar030 kaspar030 added this pull request to the merge queue Mar 1, 2024
Merged via the queue into future-proof-iot:main with commit bd55e31 Mar 1, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants