Jarek Radosz cf44cdb082
FIX: Validate category name on parent change (#10815)
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".
2020-10-05 11:50:05 +02:00
..
2020-09-01 13:41:04 +05:30
2020-04-28 15:59:39 +05:30
2019-11-29 15:49:08 +00:00
2020-07-22 16:02:31 +05:30
2020-08-21 11:36:53 +08:00
2020-09-10 13:41:46 +10:00
2019-10-21 12:08:20 +01:00
2019-05-13 15:24:24 +01:00
2020-05-05 13:46:57 +10:00
2020-09-01 13:41:04 +05:30
2020-09-01 13:41:04 +05:30
2020-09-01 13:41:04 +05:30
2020-09-01 13:41:04 +05:30
2020-05-27 19:05:24 +05:30
2020-09-01 10:22:32 +05:30
2020-04-28 15:59:39 +05:30
2019-10-17 16:58:22 +11:00