Renaming files, pos-cli clean
April 6, 2020
IMPROVED
- Moving / renaming names - improved mechanism of detecting which resource to update when either the physical file path or the
name
property changes to avoid creating duplicates and raise validation uniqueness errors. For example, when you move a file from:modules/my_modules/public/form_configurations/my_form.liquid
tomodules/my_modules/private/forms/my_form.liquid
, we will recognize this is the same file (public
changed toprivate
andform_configurations
changed toforms
), even if thename
property changes within the filemodules/my_modules/private/forms/my_form.liquid
tomodules/my_modules/private/forms/some_dir/my_form.liquid
, we will recognize this is the same file (moved the file into a new directorysome_dir
), but only if thename
property will not change
Additionally, we will also correctly recognize the file if you change the name
property without changing the file's location. However, it is allowed to update the deprecated directory name to the new one, as well as to move file from public to private and vice versa - as described in the first example.
FIXED
- Fixed edge case scenario of creating a User Profile via GraphQL mutation, then exporting the data and trying to import it, which was causing a 500 error