Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update description field in Plan entity to accept a list of strings #98

Closed
wants to merge 1 commit into from

Conversation

MonishK2002
Copy link
Contributor

Description:

This PR updates the description field in the Plan entity to accept a list of strings instead of a single string with a 100-character limit.

Reason for Update:

The current limitation of 100 characters for the description field restricts the amount of information that can be provided for each plan. Allowing the description field to accept a list of strings will enable more detailed and structured descriptions.

Changes Made:

Modified the description field in the Plan entity to be a list of strings. Updated the relevant validation logic to handle the new data type. Adjusted the database schema to support storing a list of strings for the description field. Updated the necessary documentation to reflect the changes.

Testing:

Ensured that existing plans with a single string description are migrated correctly. Validated that new plans can be created with a list of strings as the description. Verified that the updated description is correctly displayed in the user interface.

Impact:
This update ensures that plan descriptions can be more detailed and organized, providing better clarity and flexibility for users.

Description: This PR updates the description field in the Plan entity to accept a list of strings instead of a single string with a 100-character limit.

Reason for Update: The current limitation of 100 characters for the description field restricts the amount of information that can be provided for each plan. Allowing the description field to accept a list of strings will enable more detailed and structured descriptions.

Changes Made:

Modified the description field in the Plan entity to be a list of strings.
Updated the relevant validation logic to handle the new data type.
Adjusted the database schema to support storing a list of strings for the description field.
Updated the necessary documentation to reflect the changes.
Testing:

Ensured that existing plans with a single string description are migrated correctly.
Validated that new plans can be created with a list of strings as the description.
Verified that the updated description is correctly displayed in the user interface.
Impact: This update ensures that plan descriptions can be more detailed and organized, providing better clarity and flexibility for users.
@hsluoyz
Copy link
Member

hsluoyz commented Dec 11, 2024

@MonishK2002

  1. Don't create duplicated PRs like: Update description field in Plan entity to accept a list of strings #97. Update on this one
  2. Don't use ChatGPT to write messages. Leave empty if you don't want to write
  3. Pass all CI errors

@hsluoyz
Copy link
Member

hsluoyz commented Dec 12, 2024

description is string

@hsluoyz hsluoyz closed this Dec 12, 2024
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.

2 participants