[KZL-522] Collection specifications methods cloisoned to a collection #1300
Conversation
Codecov Report
@@ Coverage Diff @@
## 1-dev #1300 +/- ##
==========================================
+ Coverage 93.84% 93.85% +<.01%
==========================================
Files 98 98
Lines 6857 6862 +5
==========================================
+ Hits 6435 6440 +5
Misses 422 422
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## 1-dev #1300 +/- ##
==========================================
+ Coverage 93.84% 93.85% +<.01%
==========================================
Files 98 98
Lines 6857 6862 +5
==========================================
+ Hits 6435 6440 +5
Misses 422 422
Continue to review full report at Codecov.
|
| @@ -153,7 +153,10 @@ module.exports = [ | |||
| {verb: 'post', url: '/credentials/:strategy/_me/_create', controller: 'auth', action: 'createMyCredentials'}, | |||
| {verb: 'post', url: '/credentials/:strategy/_me/_validate', controller: 'auth', action: 'validateMyCredentials'}, | |||
|
|
|||
| /* DEPRECATED - will be removed in v2 */ | |||
There was a problem hiding this comment.
(open to debate)
since this deprecation notice is introduced so late in the v1, I wonder if this shouldn't stay for the next major version
Usually, you deprecate something during a major, it stays in the next one, and (sometimes) removed after that
There was a problem hiding this comment.
Since there is only very few people that use the validation module I think we can remove this route.
If we setup a compat configuration option (cf trello) users will be able to keep deprecated route if they want but IMHO it's better to push users to embrace change
## What does this PR do? - Update the API documentation because of this PR: kuzzleio/kuzzle#1300 ### How should this be manually tested? - Step 1 : `npm install && npm run dev` - Step 2 : visit http://localhost:8080/core/1/api/api-reference/controller-collection/validate-specifications/ - Step 3 : visit http://localhost:8080/core/1/api/api-reference/controller-collection/update-specifications/
Release 1.8.0
Bug fixes
[ #1311 ] Fix promise leaks (scottinet)
[ #1298 ] Fix disabled protocol initialization (Aschen)
[ #1297 ] Fix timeouts on plugin action returing the request (benoitvidis)
[ #1288 ] Fix an error when trying a non-partial bulk update (scottinet)
[ #1286 ] Allows bulk inserts on aliases (benoitvidis)
[ #1282 ] Scan keys on redis cluster (benoitvidis)
[ #1279 ] Users must be authenticated to use auth:logout (scottinet)
New features
[ #1315 ] Add the new Vault module to handle encrypted application secrets (Aschen)
[ #1302 ] Add write and mWrite (Aschen)
[ #1305 ] Add pipes & hooks wildcard event (thomasarbona)
Enhancements
[ #1318 ] Add a maximum ttl to auth:login (benoitvidis)
[ #1301 ] Upgrade the WebSocket libraries (scottinet)
[ #1308 ] Events triggering refactor (scottinet)
[ #1300 ] Collection specifications methods cloisoned to a collection (thomasarbona)
[ #1295 ] Improve validation error messages (benoitvidis)
[ #1292 ] Throw an error when the realtime controller is invoked by plugin developers (benoitvidis)
[ #1257 ] Add ability to define mapping policy for new fields (Aschen)
[ #1291 ] Fix --help on subcommands (Yoann-Abbes)
[ #1289 ] Handle ping/pong packets (scottinet)
[ #1273 ] Fix incomplete access logs (scottinet)
Others
[ #1317 ] Add ps dependency to plugin-dev Docker image for pm2 (benoitvidis)
[ #1312 ] Check that .kuzzlerc.sample is well-formed (scottinet)
[ #1299 ] Add Kuzzle Nightly & Redis 3 and 4 test (alexandrebouthinon)
What does this PR do ?
Validate specifications:
http://kuzzle:7512/<index>/<collection>/_validateSpecificationshttp://kuzzle:7512/_validateSpecificationsUpdate specifications:
http://kuzzle:7512/<index>/<collection>/_specificationshttp://kuzzle:7512/_specificationsHow should this be manually tested?