1971 other user settings on UI

[corlard3y]

Pull Request Template

Ticket Number

• Ticket Number

Description

• Problem/Feature:

Type of Change

• Bug fix
• New feature
• Code refactor
• Documentation update
• Other (please describe):

Checklist

• Quick PR: Is this a quick PR? Can be approved before finishing a coffee.
  • Quick PR label added
• Not Merge Ready: Is this PR dependent on some other PR/tasks and not ready to be merged right now.
  • DO NOT Merge PR label added

Frontend Guidelines

• Followed frontend guidelines as per the Guidelines Notion Doc

Build & Testing

• No errors in the build terminal
• Engineer has tested the changes on their local environment
• Engineer has tested the changes on deploy preview

Screenshots/Video with Explanation

• Before: Explain the previous behavior

• After: What's changed now

Additional Context

Review & Approvals

• Self-review completed
• Code review by at least one other engineer
• Documentation updates if applicable

Notes

[github-actions]

In the UpgradePlanModal component:

1. The planFeatures array is missing curly braces {} around the objects.
2. The closing tag for cancelButtonProps is missing in the Modal component.

In the UserPlanAndBillings component:

1. In the Box component, there is an extra opening angle bracket '<' before the second Box component.
2. The closing tag for the Text component is missing after the Upgrade Plan text.
3. The variant 'bm-regular' in the Text component should be 'bs-regular'.
4. In the ProgressBar component, the progress value is hard-coded to 250, it should be dynamic based on the item's subtitle.
5. The closing angle bracket '>' is missing in multiple places.
6. The variant 'c-bold' in the Text component should be 'h4-semibold'.
7. The CSS prop should have the correct property name which is 'cursor', instead of 'coursor'.
8. The closing tag for the Button component is missing after the Upgrade Plan button.

In the Themization.js file:

1. The object ends with a comma after the last key-value pair which can cause potential issues.
2. The missing export keyword before the export statement.

All looks good.