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

Greeter #3

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Greeter #3

wants to merge 2 commits into from

Conversation

StephaneBereux
Copy link
Owner

st'

@StephaneBereux
Copy link
Owner Author

/review

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Review summary

Thanks for the PR 🙏

Critical PR sections

  • [class-naming] detected in my_lib/users.py:L9
  • [interface-deprecation] detected in my_lib/users.py:L9

PR overview

  • 1 comment about [class-naming]
  • 1 comment about [interface-deprecation]

Add the following reactions to this comment to let us know if:

  • 😕 the review missed something important



def greet_contributor(name: str) -> str:
"""Creates a string message to greet the contributor.
class userGreeter:
Copy link

Choose a reason for hiding this comment

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

Let's use the regular PascalCase convention for classes

Pattern explanation 👈 Check here for reference.

Replacement example

Here is an example of how you could handle this:

class ModuleParser:
	def __init__(self, path: Path) -> None:
		self.path = path

This comment is about [class-naming]. Add the following reactions on this comment to let us know if:

  • 👀 that doesn't seem right
  • 👎 this isn't important for you right now
  • 😕 that explanation wasn't clear



def greet_contributor(name: str) -> str:
Copy link

Choose a reason for hiding this comment

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

This renaming seems to be introducing a breaking change 😅

Pattern explanation 👈 Breaking changes are modifications of the code base that can cause crashes for a reliant piece of code that hasn't been updated. Check here for reference.

This comment is about [interface-deprecation]. Add the following reactions on this comment to let us know if:

  • 👀 that doesn't seem right
  • 👎 this isn't important for you right now
  • 😕 that explanation wasn't clear

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