Joffrey JAFFEUX ad7d5426d8 FIX: supports groups field in post_created_edited (#28783) ... ⚠️ This commit is a revert of a revert due to a migration which was causing `{}` metadata to be transformed into `{"value": [null]}`. The new migration shouldn't cause this and will also clean the existing errors, there shouldn't be any data loss given the affected fields where not containing actual data. We might want to stop storing these empty fields in the future. To achieve it, this commit does the following: - create a new `groups field`, ideally we would have reused the existing group field, but many automations now have the expectation that this field will return a group id and not an array of group ids, which makes it a dangerous change - alter the code in `post_created_edited` to use this new groups field and change the logic to use an array - migrate the existing group fields post_created_edited automations to change name from `restricted_group` to `restricted_groups`, the component from `group` to `groups` and the metadata from `{"value": integer}` to `{"value": [integer]}` <!-- NOTE: All pull requests should have tests (rspec in Ruby, qunit in JavaScript). If your code does not include test coverage, please include an explanation of why it was omitted. -->		2024-09-06 17:22:42 +02:00
..
migrate	FIX: supports groups field in post_created_edited (#28783)	2024-09-06 17:22:42 +02:00
post_migrate