refactor: remove redundant /api/ prefix from routes #169
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.
Fixes #168
Summary
Removes the redundant
/api/prefix from all routes. Routes are now accessible at/v1/*instead of/api/v1/*, aligning internal routing with production API URLs.Breaking Changes
/v1/*instead of/api/v1/*Impact: Since we're v0.x.x, breaking changes are allowed per semantic versioning.
Changes
apiPrefix: ''inbootstrap/app.php(Laravel 12 configuration)/api/v1/*to/v1/*/api/healthto/healthRationale
Before (Inconsistent):
/api/v1/usershttps://api.secpal.app/v1/users/api/only exists internally!After (Consistent):
/v1/usershttps://api.secpal.app/v1/usersQuality Checks
Why Now?
This was identified during PR #162 where we had to fix 9 documentation files because they incorrectly documented the API as using
/api/v1/prefix. The root cause was this routing inconsistency.Related