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

Add eventpost functionality #231

Merged
merged 5 commits into from
Dec 13, 2021
Merged

Add eventpost functionality #231

merged 5 commits into from
Dec 13, 2021

Conversation

KeremZaman
Copy link
Collaborator

  • Search functionality was implemented.
  • Unit tests were added.
  • Dockerfile and django settings were changed to run tests.
  • A critical bug caused by default value of date fields was fixed.

@CenekSanzak I also added you as reviewer for reviewing if it's compatible with current API calls made by frontend.

Kerem Zaman added 4 commits December 12, 2021 16:52
- Add filtering by query, player capacity, spectators capacity, number of players, number of spectators, location name, event date, creation date, duration of the event, sport type, event owner, age, coordinates, skill levels

- Make relative imports absolute
- Add unittests for event search functionality
- Configure test database
- Convert relative imports to absolute imports in serializers.py
- Add testing command to run tests before starting application
- Add wait_for_db script for backend service to wait until database is ready
test_filter_by_date was failing due to the default value of the date field in EventPost model. By quoting the related part about auto_now_add from django documentation:
" So even if you set a value for this field when creating the object, it will be ignored."

Since the dates specified for the sample events created for tests were ignored, date_by_filter test was failing. This bug would cause wrong event dates while user creating an event, it is fixed by changing default value to the time of the event creation.
Copy link
Collaborator

@CenekSanzak CenekSanzak left a comment

Choose a reason for hiding this comment

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

I reviewed your get method. The field names and the filters seem well. We can use the function in the frontend app.

@supiket supiket self-requested a review December 13, 2021 16:41
Copy link
Contributor

@supiket supiket left a comment

Choose a reason for hiding this comment

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

I have reviewed and approved PR #237, which is based on this PR. Hence, here is my +1 on this PR's approvals.

@KeremZaman KeremZaman removed the request for review from ege-kaya December 13, 2021 16:42
@KeremZaman KeremZaman merged commit f500d43 into development Dec 13, 2021
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.

None yet

3 participants