Strict Naming convention #4
Open
Conversation
This file contains hidden or 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
* Lesson 5 * Lesson 6 * Lesson 7 * Lesson 8 * Lesson 9 * Lesson 10 * Lesson 11 * Lesson 12
* Lesson 5 * Lesson 6 * Lesson 7 * Lesson 8 * Lesson 9 * Lesson 10 * Lesson 11 * Lesson 12 * Lesson 13 * Lesson 14 * Lesson 15 * Lesson 16 and 17
We are using OOP. And from onset you have been strict on the naming convention. Should we be worried of a duplicate class. I don't see that happening.
ghost
mentioned this pull request
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We are using OOP. And from onset you have been strict on the naming convention. Should we be worried of a duplicate class. I don't see that happening.