Feature/add description field to meeting model #135
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
…ting model The 'TeamMeeting' model now includes an optional 'description' field. This change allows for additional information to be provided about the team meeting, if necessary.
The migration.sql file adds a new column "description" of type TEXT to the "TeamMeeting" table. This allows for an optional description field to be associated with each meeting in the model. This change enhances the flexibility and usability of the meeting model by providing a way to include additional information about each meeting.
…ontext The meeting seed data now includes a description field to provide more information and context about each meeting. This improves the overall quality of the seed data and makes it more useful for testing and development purposes.
…se and MeetingResponseWithSprintAndAgenda classes for better representation of meeting descriptions The MeetingResponse and MeetingResponseWithSprintAndAgenda classes now have a description property. This allows for a more comprehensive representation of meeting objects by including a detailed description of the meeting.
…TeamMeeting and updateTeamMeeting methods The createTeamMeeting and updateTeamMeeting methods in the SprintsService now support the description field in the CreateTeamMeetingDto and UpdateTeamMeetingDto respectively. This allows users to provide a description for team meetings, providing more context and information about the meeting.
…MeetingDto for better meeting information The CreateTeamMeetingDto now includes a description field, which allows users to provide a detailed description of the meeting. This improves the information available for each team meeting and provides more context for participants.
…n e2e tests The e2e tests for the Sprints Controller now include a description field in the sprint objects. This change ensures that the description field is properly tested and validated in the controller's endpoints.
The meeting model schema has been updated to include an optional description field. This change was made in PR #135.
cherylli
reviewed
Apr 17, 2024
|
Everything else works fine, all tests passed |
… description property in CreateTeamMeetingDto The @IsOptional() decorator is added to the description property in the CreateTeamMeetingDto class. This change allows the description property to be optional when creating a team meeting.
|
I have added |
JoshuaHinman
approved these changes
Apr 19, 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
This PR adds an optional description field to the meeting model schema, which allows users to provide a detailed description of the meeting. This improves the information available for each team meeting and provides more context for participants.
Issue link
Fixes # (issue)
Type of change
How Has This Been Tested?
Checklist: