-
Notifications
You must be signed in to change notification settings - Fork 3
Stage & Crew features #692
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
base: dev
Are you sure you want to change the base?
Conversation
Test Results26 tests 26 ✅ 3s ⏱️ Results for commit 86c664a. ♻️ This comment has been updated with latest results. |
86c664a to
9c53aa8
Compare
Client Test Results83 tests 83 ✅ 0s ⏱️ Results for commit 1e0bc48. ♻️ This comment has been updated with latest results. |
Python Test Results 1 files 1 suites 46s ⏱️ Results for commit 1e0bc48. ♻️ This comment has been updated with latest results. |
9c53aa8 to
31fc319
Compare
1. ruff format and fix 2. regenerate alembic revision 3. use sqlalchemy 2 syntax 4. lint front end code
Also refactor existing controllers and front end to use query param delete.
1decc8c to
8866f5f
Compare
Add tests for CrewController, PropTypesController, PropsController, SceneryTypesController, and SceneryController covering GET, POST, PATCH, and DELETE operations including validation and error handling. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Change the crew deletion endpoint to accept the ID via query parameter instead of JSON body, aligning with HTTP DELETE best practices and the pattern used by other stage controllers (props, scenery, allocations). Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
No description provided.