Skip to content

Conversation

@daniel-su1
Copy link
Collaborator

Notion ticket link

Ticket Name

Implementation description

Steps to test

What should reviewers focus on?

Checklist

  • My PR name is descriptive and in imperative tense
  • My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
  • I have run the appropriate linter(s)
  • I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

- Updated server.py to include user_data routes.
- Modified models/__init__.py to export UserData model.
- Enhanced User model to establish a relationship with UserData.
- Introduced user_data_service for handling UserData operations.

This commit integrates UserData functionality into the backend, allowing for better user data management.
- Reformatted method signatures and SQLAlchemy model definitions for better clarity.
- Ensured consistent line endings and spacing across user data service and related files.
- Updated exception handling messages for better readability in the user data service implementation.
…data modules

- Removed unused UserRole import from auth middleware.
- Reordered SQLAlchemy imports in UserData model for better organization.
- Ensured consistent import structure in service utilities by adjusting import order.
- Updated UserDataBase schema to accept preferences as either a comma-separated string or a list of strings.
- Implemented a new internal helper method in UserDataService to serialize preferences into a consistent format for database storage.
- Adjusted user data retrieval and creation methods to ensure preferences are correctly formatted before database operations.
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.

1 participant