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

Implemented: Validations and model spec #3

Merged
merged 3 commits into from
Jan 18, 2023
Merged

Conversation

Strangeal
Copy link
Owner

In this PR, I added RSpec to this project to write test for models and also added some validations as per requirements. Below are the features I added:

  • Added validations for User and Post models:
    • Name and Title must not be blank.
    • Title must not exceed 250 characters.
    • PostsCounter, CommentsCounter and LikesCounter must be an integer greater than or equal to zero.
  • Added unit specs for all my models, methods and validations.

Copy link

@GzimAsani GzimAsani left a comment

Choose a reason for hiding this comment

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

Hello @Strangeal 👋

Good job so far! There are some issues that you still need to work on to go to the next project but you are almost there!

Highlights

  • Good job with your testing 👍

Required Changes

  • On your readme file please let the potential users know how they can test your app and what are the prerequisites to install in order to test.

Optional suggestions

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.

Cheers and Happy coding! clapclapclap

Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Copy link

@mahbubul14 mahbubul14 left a comment

Choose a reason for hiding this comment

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

Project Approved 🏆 🎉

Hi @Strangeal,

Your project is complete! You have done it exceptionally well. it's time to merge it 💯
Congratulations! 🎉

To Highlight 👍

✔️ No linter error.
✔️ Descriptive readme file.
✔️ Well-implemented suggestions.

Optional suggestions 🔽

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you take them into account as they can make your code better.

  • The commit message should be written in the imperative tense and the first letter should also be capitalized. Ex: "Fix bug" instead of "fix bug". For more details...

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification. You can also connect with me on slack


As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

@Strangeal
Copy link
Owner Author

@mahbubul14 Thank you

@Strangeal Strangeal merged commit b63011f into dev Jan 18, 2023
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.

3 participants