Solo project GET all endpoint #223
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… formatting logic to improve code clarity and maintainability feat(solo-projects.service.ts): add UserWithProfile and SoloProjectWithPayload types to enhance type safety and data handling
…grity refactor(services): simplify user selection in SoloProject service and include comments and status for enhanced project details
…for testing feat(controllers): implement pagination for fetching solo projects with offset and page size refactor(services): update getAllSoloProjects method to support pagination and return metadata along with data
…to feature/solo-project-endpoints
…categories to voyage teams feat(src/solo-projects/solo-projects.controller.ts): add support for sorting solo projects by status, createdAt, and updatedAt feat(src/solo-projects/solo-projects.service.ts): implement sorting of solo projects based on the provided sort parameter The changes in this commit are as follows: 1. In the `prisma/seed/voyage-teams.ts` file, the `populateVoyageTeams` function was updated to add tech stack categories to the voyage teams. This will allow the application to associate specific tech stacks with each voyage team. 2. In the `src/solo-projects/solo-projects.controller.ts` file, the `getAllSoloProjects` method was updated to accept a new `sort` query parameter. This parameter allows the client to sort the solo projects by status, createdAt, and updatedAt in ascending or descending order. 3. In the `src/solo-projects/solo-projects.service.ts` file, the `getAllSoloProjects` method was updated to handle the sorting of solo projects based on the provided `sort` parameter. This will enable the application to display the solo projects in the desired order. These changes will improve the functionality of the application by allowing users to better manage and organize the solo projects, as well as associate relevant tech stacks with the voyage teams.
…clude responseGroup and its responses feat(solo-projects.service.ts): add responseGroup and its responses to the formatted solo project data chore(solo-projects.e2e-spec.ts): add empty e2e test file for solo projects
…input type to solo project form fix(prisma/seed/responses/helper.ts): remove unnecessary console.log statement feat(prisma/seed/solo-project.ts): add new solo project with option choices for "Tier" question feat(src/global/global.service.ts): add new formatResponses function to transform response data into a more readable format feat(src/solo-projects/solo-projects.service.ts): update formatSoloProject function to use the new formatResponses function and include the input type information for each question
…d github profile information from user's OAuth profiles feat(global/selects/users.select.ts): add providerUserId field to user OAuth profile select feat(global/types/users.types.ts): add providerUserId field to UserWithProfile type feat(solo-projects/solo-projects.controller.ts): add ApiResponse for getAllSoloProjects endpoint to document the response schema feat(solo-projects/solo-projects.response.ts): create a response DTO to document the structure of the solo projects response refactor(solo-projects/solo-projects.service.ts): update the formatSoloProject method to include createdAt and updatedAt fields in the response
…ent class to support nested comments feat(solo-projects.response.ts): add SoloProjectResponseMeta class to encapsulate pagination metadata feat(solo-projects.response.ts): update SoloProjectsResponse class to include data and meta properties for a more structured response
…uestException for invalid sort field refactor(pipes): remove IntDefaultValuePipe and replace it with NonNegativeIntDefaultValuePipe to handle negative values feat(solo-projects.controller.ts): add Swagger documentation for the getAllSoloProjects endpoint, including error responses
…to feature/solo-project-endpoints
|
@timDeHof, @JoshuaHinman |
timDeHof
approved these changes
Nov 22, 2024
JoshuaHinman
approved these changes
Nov 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add GET endpoint for solo project. Authorization, e2e tests, and unit tests will be done in the next PR.
I'm unsure what is the best way to format the comments, now they are just all included. There are a few options I've considered, noted in google docs, which can be updated later on
Issue link
https://app.clickup.com/t/86b1dafqa
Type of change
How Has This Been Tested?
Tested on swagger, ran all the tests to make sure existing tests pass
Checklist: