mirror of
https://github.com/Unleash/unleash.git
synced 2025-09-19 17:52:45 +02:00
5cdb3f665a
* task: Ban changes to variants through feature After adding the new `/variants` endpoint for features we now have a way to access control adding/modifying variants, so the /:featureName endpoint should no longer allow editing/adding variants. This removes variants as a known field from the featureMetadata schema and tells joi to stripUnknown, thus making sure we never include variants in the initial creation or future update calls. For the old features v1 API we allow it to declare that it has already validated the data coming with its own schema, so we should use the data we get from it. Thus keeping the old v1 functionality intact Co-authored-by: Simon Hornby <simon@getunleash.ai> |
||
|---|---|---|
| .. | ||
| bad-data-error.ts | ||
| db-error.ts | ||
| feature-has-tag-error.ts | ||
| incompatible-project-error.ts | ||
| invalid-operation-error.ts | ||
| invalid-token-error.ts | ||
| minimum-one-environment-error.ts | ||
| name-exists-error.ts | ||
| no-access-error.ts | ||
| notfound-error.ts | ||
| operation-denied-error.ts | ||
| owasp-validation-error.ts | ||
| password-undefined.ts | ||
| used-token-error.ts | ||