| .. |
|
api-def.json
|
chore(modernize): cleanup api-def
|
2018-12-17 08:27:49 +01:00 |
|
archive.js
|
Refactored controllers, moved checkPermission to permission-checker.js middleware
|
2019-01-17 09:25:12 +01:00 |
|
archive.test.js
|
Use full name instead of perms, 403 error message now includes expected permission
|
2019-01-17 09:25:12 +01:00 |
|
event.js
|
Refactored controllers, moved checkPermission to permission-checker.js middleware
|
2019-01-17 09:25:12 +01:00 |
|
events.test.js
|
chore: Upgrade ava to 1.0.1
|
2018-12-17 10:16:18 +01:00 |
|
feature-schema.js
|
fix: Update variant protocol
|
2019-02-08 09:38:23 +01:00 |
|
feature-schema.test.js
|
chore: Upgrade ava to 1.0.1
|
2018-12-17 10:16:18 +01:00 |
|
feature.js
|
Refactored controllers, moved checkPermission to permission-checker.js middleware
|
2019-01-17 09:25:12 +01:00 |
|
feature.test.js
|
fix: Update variant protocol
|
2019-02-08 09:38:23 +01:00 |
|
index.js
|
Refactored controllers, moved checkPermission to permission-checker.js middleware
|
2019-01-17 09:25:12 +01:00 |
|
metrics-schema.js
|
feature: Add action specific user permissions
|
2019-01-17 09:25:12 +01:00 |
|
metrics.js
|
Refactored controllers, moved checkPermission to permission-checker.js middleware
|
2019-01-17 09:25:12 +01:00 |
|
metrics.test.js
|
Use full name instead of perms, 403 error message now includes expected permission
|
2019-01-17 09:25:12 +01:00 |
|
strategy-schema.js
|
chore(modernize): Use joi for url-friendly name validation
|
2018-12-17 08:27:49 +01:00 |
|
strategy.js
|
Refactored controllers, moved checkPermission to permission-checker.js middleware
|
2019-01-17 09:25:12 +01:00 |
|
strategy.test.js
|
Use full name instead of perms, 403 error message now includes expected permission
|
2019-01-17 09:25:12 +01:00 |
|
user.js
|
Refactored controllers, moved checkPermission to permission-checker.js middleware
|
2019-01-17 09:25:12 +01:00 |
|
user.test.js
|
chore: Upgrade ava to 1.0.1
|
2018-12-17 10:16:18 +01:00 |
|
util.js
|
fix(http-status): Client errors should use 400 status codes
|
2019-01-02 12:38:58 +01:00 |
