📝 [New chapter] R coding style #216
Open
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
SaranjeetKaur
changed the title
|
Also tagging @jyoti-bhogal for a review as she was interested in this issue. |
hturner
reviewed
Dec 6, 2024
| - Use `TRUE` and `FALSE`, not `T` and `F`. | ||
| - Keep lines no longer than 80 characters. | ||
| - Avoid using special characters in file names (numbers, letters, `-`, and `_` are acceptable). | ||
| - Put a space after (not before) a comma. |
There was a problem hiding this comment.
already have this as second point
Suggested change
| - Put a space after (not before) a comma. |
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.
Closes #133
This PR adds a new chapter on R coding style.