Coding conventions #102
Merged
Coding conventions #102
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
Joelius300
force-pushed
the
coding-conventions
branch
from
6977880 to
6e3fa6c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new file with the coding conventions discussed in #58 and Joelius300/ChartJSBlazor#22. I think we should try to comply with these conventions from now on. I know that there are still lots of inconsistencies around that topic but it's time to write this stuff down and try to get more consistent at it. Maybe we'll do a big overhaul to fix it everywhere but that's a lot of work; I'm not sure if we'll do that.
You can view the file as rendered markdown (HTML) here.
I'm open for feedback and would love to hear your opinions on those conventions.
Fixes #58