Skip to content

WIP: fix(backend-test): the validation should not return None #669

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

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

Conversation

MitanOmar
Copy link
Member

No description provided.

@MitanOmar MitanOmar requested a review from a team as a code owner March 24, 2025 16:40
@MitanOmar MitanOmar marked this pull request as draft March 24, 2025 16:40
@MitanOmar MitanOmar changed the title DRAFT: fix(backend-test): the validation should not return None WIP: fix(backend-test): the validation should not return None Mar 24, 2025
@MitanOmar MitanOmar marked this pull request as ready for review April 10, 2025 13:04
@MitanOmar MitanOmar enabled auto-merge (squash) April 10, 2025 13:05
@@ -184,7 +184,7 @@ def validate(self, data):
.exists()
):
return data
msg = "You don't have the permission to update this task"
msg = "You don't have the permission to update this task" # pragma: no cover
Copy link
Member

Choose a reason for hiding this comment

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

I'd rather see a test for this instead

Copy link
Member Author

Choose a reason for hiding this comment

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

@winged i did not see tests in the beginning, that's why i did not wrote it, but for sure i can add,
and an important note: i see in the changes tab that the changes are only one file, but if you check f0785a2 commit, you will see that there are some snapshot updated, i would like to confirm this too please

Copy link
Member

Choose a reason for hiding this comment

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

It's a change in behaviour, so I think there should be a test for it.

Regarding that commit, I think it's coming from the main branch as you merged main into this feature branch, so that's normal. Maybe try rebasing, then the diff should be less confusing

@c0rydoras
Copy link
Collaborator

Just a couple questions:

  • what was the motivation for this
  • why is everything noqa'd? if we add new/improved functionality, testing it should be a given?

:)

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