-
- Downloads
First stage of refactor targeting simplicity
Structure flow around requests themselves and composition rather than handlers and wrappers, the results are likely more readable (and shorter). Move all the user auth management business logic to a smart RawUser object, to separate it from details of API handling. The result should be more understandable: all critical changes are contained within a single type. Also, with all the workflow driven by Requests, we can get rid of the boilerplate in the HTTP API server and replace it with a tiny tiny layer of reflection.
Showing
- actions.go 140 additions, 853 deletionsactions.go
- actions_create.go 209 additions, 0 deletionsactions_create.go
- actions_resource.go 190 additions, 0 deletionsactions_resource.go
- actions_test.go 142 additions, 108 deletionsactions_test.go
- actions_user.go 373 additions, 0 deletionsactions_user.go
- audit.go 18 additions, 10 deletionsaudit.go
- backend/model.go 23 additions, 35 deletionsbackend/model.go
- backend/model_test.go 6 additions, 6 deletionsbackend/model_test.go
- backend/testdata/test1.ldif 6 additions, 9 deletionsbackend/testdata/test1.ldif
- backend/tx.go 1 addition, 1 deletionbackend/tx.go
- cmd/accountserver/main.go 1 addition, 1 deletioncmd/accountserver/main.go
- encryption.go 0 additions, 71 deletionsencryption.go
- errors.go 37 additions, 4 deletionserrors.go
- integrationtest/integration_test.go 76 additions, 62 deletionsintegrationtest/integration_test.go
- integrationtest/testdata/test1.ldif 6 additions, 8 deletionsintegrationtest/testdata/test1.ldif
- server/server.go 85 additions, 176 deletionsserver/server.go
- service.go 48 additions, 279 deletionsservice.go
- types.go 268 additions, 0 deletionstypes.go
Loading
Please register or sign in to comment