Add school management REST API and architecture checks
This commit is contained in:
25
CHANGELOG.md
Normal file
25
CHANGELOG.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# Changelog
|
||||
|
||||
## [1.0] - 2026-10-27
|
||||
|
||||
### Added
|
||||
|
||||
- Quarkus backend running on Java 25, with health endpoints and Docker support.
|
||||
- Domain model for dance schools, dancers, dance groups, coaches, shows and day parts.
|
||||
- REST API to create, list, retrieve, update and delete dance schools, dancers, dance groups and shows.
|
||||
- Membership management allowing a dancer to belong to multiple groups within a school.
|
||||
- Shows with a name, date and three day parts: morning, afternoon and evening.
|
||||
- Input validation, school-scoped resource access and cleanup of memberships when dancers are deleted.
|
||||
- Shared in-memory storage for the REST API.
|
||||
- Separate API model records in `rest.apimodel`.
|
||||
- ArchUnit checks for package dependencies, domain independence, package cycles and API model conventions.
|
||||
- HTTP integration tests for resource management, memberships, validation and school isolation.
|
||||
|
||||
### Fixed
|
||||
|
||||
- Adding entities to initially empty dance school and dance group collections now retains them.
|
||||
|
||||
### Limitations
|
||||
|
||||
- Data is lost when the application stops.
|
||||
- Assigning dance groups to show day parts is not yet available.
|
||||
Reference in New Issue
Block a user