Two test cases for the course service failed. Could you please have a look at it whenever you can? @kerry407

Currently, the API does not support multimedia content such as videos, images, or audio files. It would be great to enhance the API to handle and serve multimedia content for a richer learning experience.

I will be writing more test cases to increase the test coverage fro the lessons feature.

Create the views, serializers and urls for Tag, TagModules and Modules with custom permissions fro write actions

Include clear contribution guidelines in the project's documentation to provide guidance to potential contributors. This will encourage collaboration and streamline the process of accepting contributions.

Currently, the API lacks an endpoint to retrieve information about users who have enrolled in a course. This functionality is important for instructors to track and manage their course enrollments effectively. We need to add an API endpoint that allows instructors to view the list of enrolled users for a specific course.

The new endpoint should provide instructors with essential details about each enrolled user, such as their username, email address, enrollment date, and progress within the course. This information will enable instructors to monitor the course's popularity, track user engagement, and tailor their teaching strategies accordingly.

It would be helpful to include filtering and pagination options in the endpoint to handle large numbers of enrolled users efficiently. Instructors should be able to filter users based on criteria such as enrollment date, completion status, or quiz scores.

To better organize user data, I suggest creating separate profile models for each user type.

Upon registration, the user would specify their role as a student or instructor using a Boolean field called "is_instructor". Then, using Django signals, the system can automatically create the appropriate profile model for the user.

I believe this change would make the project more user-friendly and efficient

Did you update requirements.txt file after creating the stripe payment?

@easonliao1994 do you have a Twitter account? I love to connect

I would like to request the addition of PageNumberPagination to the UserViewSet API in order to improve the pagination of user data.

Currently, the API returns all users in a single response, which may lead to performance issues when the number of users is large. By incorporating PageNumberPagination, we can limit the number of users returned per page and provide pagination links for easier navigation through the user data.

I propose the following changes to the UserViewSet:

from rest_framework.pagination import PageNumberPagination
class UserViewSet(AutoPrefetchViewSetMixin, viewsets.ModelViewSet):
    # ...

    # Set the pagination class and page_size
    pagination_class = PageNumberPagination
    page_size = 20
    
    # ...

By implementing pagination, we can enhance the API's performance and provide a more user-friendly experience when dealing with a large number of users.

I appreciate your consideration of this feature request. Please let me know if you have any questions or if there is any additional information I can provide to support this proposal.

Thank you!

No .env file example
Not have an example of what a typical developer should have in his/her .env file for this project in neither the repo or the readme file makes contributing to your work alot harder.
I applead to you to please fix this🤲

While the API supports payment through the Stripe API, it would be beneficial to include additional payment options to accommodate users who prefer alternative payment methods.

In user_service.views.CustomTokenObtainPairViewSet

@Benji918 could you write unit tests for the 2FA feature and ensure it is working as expected.

Add field “average_rating” as float field in Course model in ER diagram

To kickstart the Module Service app, I'll begin by creating and configuring the necessary models.

As the project grows and handles more complex tasks, it would be beneficial to incorporate Celery into the system for efficient and scalable background task processing. Celery is a powerful distributed task queue that will enable the API to handle asynchronous tasks, such as sending emails, processing large data uploads, or performing resource-intensive operations in the background.

By introducing Celery, we can improve the overall performance and responsiveness of the Smart Learning API. Tasks that may take longer to complete, such as generating reports or processing large datasets, can be offloaded to background workers, preventing delays or timeouts in the API's responses.

Some potential use cases for Celery integration include:

• Asynchronous email sending: Instead of blocking the API's response while sending emails, we can utilize Celery to handle email sending asynchronously, ensuring a smooth user experience.
• Background data processing: Celery can be used to process large data uploads, perform complex computations, or generate reports in the background without affecting the API's responsiveness.
• Scheduled tasks: We can leverage Celery's scheduling capabilities to automate periodic tasks, such as sending reminders or updating course data.

Integrating Celery into the project will require configuring a message broker, such as RabbitMQ or Redis, and setting up worker processes to handle the tasks. The implementation should also consider error handling, task monitoring, and potential security implications.

The Review field in Course which is int doesn't have a model in the ER diagram. We should create One.
{
"user": user__uuid,
"review_body": varchar,
"rating": int,
"course": course__uuid
}

Make the course difficulty an Enum/Choices instead of a positive interger.

Requesting the addition of a chat/messaging feature to enhance the functionality of the Smart Learning API. The feature would enable users and instructors to communicate with each other within the platform, facilitating better collaboration and support.

Implementing a chat/messaging feature would provide the following benefits:

• Improved User Engagement: Users and instructors can easily communicate and exchange information, fostering a more interactive learning experience.

• Real-time Support: Users can seek assistance from instructors and receive prompt responses, enhancing their learning progress.

• Seamless Collaboration: Instructors can efficiently interact with enrolled users, addressing questions, providing feedback, and facilitating discussions.

Commencement with the instructor app has begun. Will submit PR's immediately I am done with each endpoint related to instructors

Hello everyone,

I want to implement a custom user model for better user management in our project. This will allow us more control over the user model and add additional fields and functionality as needed.

Currently, we are using the default Django user model, which can be limiting for our specific use case. By implementing a custom user model, we can have a more tailored one that meets our project requirements.

How do we find resources on the API? For example, every course has one or more modules, and each module has one or more lessons. That means if we're trying to access a particular lesson, the URL should be something like this: course/module/lesson/{id}/. However, when I look at our project setup, I'm confused about how to resolve this issue.

The profile page is the personal page that viewed only by the request user (the owner of this page) because it might contain Personal and sensitive information about himself, so only this user has the full permission to view and partial update of his own data.
By the other hand, some information in this profile page might have considered as a public information of this user, so the idea of Suggestion is to create a new endpoint that will be the details of a user but with only public profile information,this endpoint can retrieve by(user_id).

I encountered an issue while running the tests. Unfortunately, the tests are not passing for me. I wanted to reach out to inquire if there are any missing dependencies or additional setup steps required to run the tests successfully.

File "/Users/eason/Desktop/github/smart_learn/user_service/serializers.py", line 74, in validate
    data = super().validate(attrs)
  File "/Users/eason/Desktop/github/smart_learn/venv/lib/python3.9/site-packages/rest_framework_simplejwt/serializers.py", line 72, in validate
    data["refresh"] = str(refresh)
  File "/Users/eason/Desktop/github/smart_learn/venv/lib/python3.9/site-packages/rest_framework_simplejwt/tokens.py", line 81, in __str__
    return self.get_token_backend().encode(self.payload)
  File "/Users/eason/Desktop/github/smart_learn/venv/lib/python3.9/site-packages/rest_framework_simplejwt/backends.py", line 113, in encode
    token = jwt.encode(
  File "/Users/eason/Desktop/github/smart_learn/venv/lib/python3.9/site-packages/jwt/api_jwt.py", line 67, in encode
    return api_jws.encode(json_payload, key, algorithm, headers, json_encoder)
  File "/Users/eason/Desktop/github/smart_learn/venv/lib/python3.9/site-packages/jwt/api_jws.py", line 153, in encode
    key = alg_obj.prepare_key(key)
  File "/Users/eason/Desktop/github/smart_learn/venv/lib/python3.9/site-packages/jwt/algorithms.py", line 186, in prepare_key
    key = force_bytes(key)
  File "/Users/eason/Desktop/github/smart_learn/venv/lib/python3.9/site-packages/jwt/utils.py", line 22, in force_bytes
    raise TypeError("Expected a string value")
TypeError: Expected a string value

Any assistance or suggestions would be greatly appreciated. Thank you for your time and support!

I noticed that the views for creating, listing, updating, and deleting InstructorSkill and SkillCertification objects are currently located in the course_service.views module, but these objects are associated with user profiles and therefore should be managed by the user_service app instead.

I recommend moving the following views to the user_service.views module and its related URL :

• InstructorSkillCreateView
• InstructorSkillListView
• InstructorSkillDetailView
• SkillCertificationCreateView
• SkillCertificationListView
• SkillCertificationDetailView

By moving these views to the appropriate app, we can improve the organization and maintainability of the project. Additionally, this will ensure that user-related objects are managed in the correct place, which can prevent confusion and errors down the line.

@chukaibejih What service are you working on?

• The README's API Endpoints section should be revised to reflect the current set of endpoints that are available in the project.
  https://github.com/chukaibejih/smart_learn#api-endpoints

• Enhance the API documentation by providing more detailed explanations of endpoints, request/response examples, and authentication requirements. This will make it easier for developers to integrate the API into their projects.

We need to take care of the N+1 query problem, where we are making N queries to retrieve N-related objects, resulting in a significant amount of extra queries and slowing down the overall performance of our API.

Improve the reporting and analytics features of the API to provide more comprehensive and detailed insights into user progress, course performance, and other relevant metrics.

Extend the API's capabilities to support multiple languages, allowing users to access course content and interact with the platform in languages other than English.

I would like to suggest implementing user registration, login, and password management functionality in our project. These features are essential for any web application that requires user authentication and will provide a better user experience for our users.

Specifically, I suggest implementing the following functionality:

1. User registration with activation: This will enable new users to create an account and activate it via a confirmation email.
2. Login/Logout: This will enable users to securely log into our application.
3. Retrieve/Update the Django User model: This will allow users to view and edit their profile information.
4. Password change: This will enable users to change their password within the application.
5. Password reset via email: This will allow users to reset their password if they forget it by sending a password reset email.

Currently, all of the tests for course_service app are in a single file. This is starting to become difficult to manage as the project grows in size and complexity. I would like to separate the test files into separate files for each module or feature. This would make it easier to find and modify tests, and would also make it easier to understand the test coverage for each module or feature.

I propose creating a new directory called "tests" inside the app directory and then creating separate Python files for each module or feature, with the tests for that module or feature contained within. This would allow us to organize tests more effectively and make them easier to manage.

What does the highlighted function do? Because all users are active = True by default even superusers and staff accounts.

Increase the test coverage of the API by writing additional test cases to ensure that all endpoints, models, and critical functionality are thoroughly tested. This will help maintain code quality and reduce the likelihood of introducing bugs in future development.