core: DB model and CRUD functionality for projects

[pingSubhajit]

This issue focuses on setting up the database model and defining the CRUD operations (Create, Read, Update, Delete) for projects within the application.

Success Criteria:

A database model for projects is defined, including the necessary fields to store project information.

• CRUD operations for projects are implemented, allowing users to create, read, update, and delete their project entries.

Acceptance Criteria:

• Database Model:
  • Project Name: (required) Unique identifier for the project.
  • Description: (optional) A brief description of the project.
  • Technologies: (optional) Array of strings representing technologies used.
  • Role: (required) User's role in the project.
  • Accomplishments: (optional) Array of strings representing key achievements or contributions.
  • Links: (optional) Array of strings representing links to the project (e.g., GitHub repository, website).
  • UserId: (required) Foreign key referencing the user who owns the project.
• CRUD Operations:
  • Create: Allows users to create new project entries, providing all required information and optionally including other fields.
  • Read: Retrieves a list of projects for a specific user.
  • Update: Allows users to modify existing project entries, updating any fields as needed.
  • Delete: Enables users to remove project entries from their profile.
• Data Validation:
  • Validate user input to ensure data integrity and prevent invalid or malicious entries.
  • Error handling is implemented to handle invalid or missing data gracefully.
• Security:
  • Implement appropriate security measures to protect project data from unauthorized access.
  • Ensure that users can only access and modify their own project entries.

Additional Notes:

• Implement appropriate authorization and authentication mechanisms to control user access to project data.
• Document the database model and CRUD operations for future development and maintenance.

This implementation will lay the foundation for managing project data within the application, providing users with a robust system for creating, updating, and deleting their project entries.

[linear]

LET-18 core: DB model and CRUD functionality for projects

This issue focuses on setting up the database model and defining the CRUD operations (Create, Read, Update, Delete) for projects within the application.

Success Criteria:

• A database model for projects is defined, including the necessary fields to store project information.
• CRUD operations for projects are implemented, allowing users to create, read, update, and delete their project entries.

Acceptance Criteria:

• Database Model:
  • Project Name: (required) Unique identifier for the project.
  • Description: (optional) A brief description of the project.
  • Technologies: (optional) Array of strings representing technologies used.
  • Role: (required) User's role in the project.
  • Accomplishments: (optional) Array of strings representing key achievements or contributions.
  • Links: (optional) Array of strings representing links to the project (e.g., GitHub repository, website).
  • UserId: (required) Foreign key referencing the user who owns the project.
• CRUD Operations:
  • Create: Allows users to create new project entries, providing all required information and optionally including other fields.
  • Read: Retrieves a list of projects for a specific user.
  • Update: Allows users to modify existing project entries, updating any fields as needed.
  • Delete: Enables users to remove project entries from their profile.
• Data Validation:
  • Validate user input to ensure data integrity and prevent invalid or malicious entries.
  • Error handling is implemented to handle invalid or missing data gracefully.
• Security:
  • Implement appropriate security measures to protect project data from unauthorized access.
  • Ensure that users can only access and modify their own project entries.

Additional Notes:

• Implement appropriate authorization and authentication mechanisms to control user access to project data.
• Document the database model and CRUD operations for future development and maintenance.

This implementation will lay the foundation for managing project data within the application, providing users with a robust system for creating, updating, and deleting their project entries.

[pingSubhajit]

In the light of the new migration strategy to a dedicated backend service, see LET-38, this issue has been cancelled