Technology Stack
- DB: Relational Records
- Server: wai
- JSON: aeson
Relational Records (HRR)
- Setup & Definition of Data Model in HRR
- CRUD Interface utilizing corresponding Haskell data types
- Error handling
- Investigate best way for DB housekeeping with HRR
Time estimate: 14 hours
Server
- Basic request routing
- Basic abstraction for REST handlers with some type safety
Time estimate: 8 hours
JSON
- Conversion to and from Haskell data types
- Basic validation
Time estimate: 4 hours
Domain API
- Implement domain REST API as per Specs on top of Server
- Tenants, Users, Roles data types
- Permission data type depending on how fast the sprint goes
- provide test cases against Domain API
Time estimate: 12 hours
The resulting Domain API should include:
- CreateRole, DeleteRole, AssignRole, RemoveRole, GetRole
- CreateUser, UpdateUser, ActivateUser, DeactivateUser, GetUser
- CreateTenant, UpdateTenant, ActivateTenant, DeactivateTenant, GetTenant
- maybe: corresponding Permission handlers (see above, point 3)
I'll commit my work to a feature branch in my fork of the haskell-webapps repository and send PRs to this one, unless desired otherwise.
Technology Stack
Relational Records (HRR)
Time estimate: 14 hours
Server
Time estimate: 8 hours
JSON
Time estimate: 4 hours
Domain API
Time estimate: 12 hours
The resulting Domain API should include:
I'll commit my work to a feature branch in my fork of the
haskell-webappsrepository and send PRs to this one, unless desired otherwise.