-
Notifications
You must be signed in to change notification settings - Fork 11
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: add editorconfig to enforce private and public member naming convention #137
Conversation
…tion Signed-off-by: Daniel Robinson <daniel.robinson@pebble.tv>
Signed-off-by: Daniel Robinson <daniel.robinson@pebble.tv>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #137 +/- ##
=======================================
Coverage 80.48% 80.48%
=======================================
Files 30 30
Lines 902 902
Branches 109 109
=======================================
Hits 726 726
Misses 122 122
Partials 54 54 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Daniel Robinson <daniel.robinson@pebble.tv>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What this PR does / why we need it
This PR adds a editorconfig file which will enforce good naming convention when using support IDEs. Thankfully most private/public members already conform to this standard.
Private = _camalCase
Public = PascalCase
Which issue(s) this PR resolves / fixes
N/A
Please check the following list