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

Refactor: Rename route from /plans to /billing-plans for clarity according to the swagger docs #636

Open
5 of 10 tasks
idehen-divine opened this issue Feb 28, 2025 · 1 comment

Comments

@idehen-divine
Copy link

Description

Renaming the route resource from /plans to /billing-plans to improve naming consistency and clarity. This ensures better maintainability and aligns with our naming conventions.

Related Issue (Link to Github issue)

N/A (New refactor request)

Motivation and Context

The current route naming is inconsistent/confusing. Renaming it to /billing-plans makes it more intuitive and aligns with the rest of our API structure.

How Has This Been Tested?

  • Updated all references in controllers and views
  • Checked for any broken links or dependencies
  • Verified functionality in Postman/browser
  • Ran existing test suite to confirm no regressions

Screenshots (if appropriate - Postman, etc):

N/A

Types of changes

  • Refactor (non-breaking change that improves maintainability)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
@idehen-divine
Copy link
Author

Image
Image

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

No branches or pull requests

1 participant