Previously, moving a category into another one, that already had a child category of that name (but with a non-conflicting slug) would cause a 500 error: ``` # PG::UniqueViolation: # ERROR: duplicate key value violates unique constraint "unique_index_categories_on_name" # DETAIL: Key (COALESCE(parent_category_id, '-1'::integer), name)=(5662, Amazing Category 0) already exists. ``` It now returns 422, and shows the same message as when you're renaming a category: "Category Name has already been taken". |
||
|---|---|---|
| .. | ||
| components | ||
| fabricators | ||
| fixtures | ||
| helpers | ||
| import_export | ||
| initializers | ||
| integration | ||
| integrity | ||
| jobs | ||
| lib | ||
| mailers | ||
| models | ||
| multisite | ||
| requests | ||
| script/import_scripts | ||
| serializers | ||
| services | ||
| support | ||
| tasks | ||
| views/omniauth_callbacks | ||
| rails_helper.rb | ||
| swagger_helper.rb | ||