Description
In this PR, we resolved an issue related to the plans we offer that aren’t displayed on the website and are used for other purposes. The point is that these plans have their own IDs and could appear at checkout, so they must be accounted for. Previously, we assumed that if a plan wasn’t one of the three we have on website, it would be the free plan and we used the 1GB path, this is no longer the case. To address this:
- We have modified the JSONs so that it is no longer the 1GB plan but the default one, we dynamically pass the size in bytes to this JSON
- We’ve also updated the checkoutProductCard so it can recognize when a plan has specific features (Array.isArray—this is done because if that’s not the case, it literally returns the path) or should use the default features. The approach for the title is the same
Related Issues
Related Pull Requests
Checklist
- Changes have been tested locally.
- Unit tests have been written or updated as necessary.
- The code adheres to the repository's coding standards.
- Relevant documentation has been added or updated.
- No new warnings or errors have been introduced.
- SonarCloud issues have been reviewed and addressed.
- QA Passed
Testing Process
We have verified that the standard plans continue to display as expected and that these special plans are now being displayed. Examples:
- planId=price_1RjEJPFAOdcgaBMQifUoiJgL
- planId=price_1RBxrfFAOdcgaBMQxbEQlLsI