-
Notifications
You must be signed in to change notification settings - Fork 0
feat(api): rename /config to /setup #70
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
|
|
@@ -23,7 +23,7 @@ app.get('/health', (c) => { | |||||||
| // Mount route apps | ||||||||
| app.route('/api-keys', apiKeysApp); | ||||||||
| app.route('/calibration', calibrationApp); | ||||||||
| app.route('/config', configApp); | ||||||||
| app.route('/setup', configApp); | ||||||||
|
||||||||
| app.route('/setup', configApp); | |
| app.route('/setup', configApp); | |
| app.route('/config', configApp); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are app-level Vitest smoke tests (e.g.,
/health, 404), but nothing asserting that the config download route is mounted at the new/setuppath. Adding a simple test that/setupresponds (e.g., 401 for missing/invalid key) would prevent regressions on future route refactors.