Do not use constant AUN_CASE_LEAVE_ASIS in auto_username.settings.yml

@Liam Morland: is this still a problem now that 📌 Refactor legacy code and fix phpcs issues Active has been committed?

I am not familiar with the !php/const syntax, but it looks plausible. If it does what it appears to do, then it will fix this.

I got this error on update drupal or install new module:

Drupal\Core\Config\UnsupportedDataTypeConfigException: Invalid data type in config auto_username.settings, found in file modules/contrib/auto_username/config/install/auto_username.settings.yml: The string "!php/const Drupal\auto_username\AutoUsernamePunctuationOptions::CASE_LEAVE_AS_IS" could not be parsed as a constant.

I installed lastest dev version but #3391633 didn't solved the problem.

I changed

aun_case: !php/const Drupal\auto_username\AutoUsernamePunctuationOptions::CASE_LEAVE_AS_IS

to

aun_case: 0

error is gone.

Got error when enabled the module :

Drupal\Core\Config\UnsupportedDataTypeConfigException: Invalid data type in config auto_username.settings, found in file modules/contrib/auto_username/config/install/auto_username.settings.yml: The string "!php/const Drupal\auto_username\AutoUsernamePunctuationOptions::CASE_LEAVE_AS_IS" could not be parsed as a constant. Did you forget to pass the "Yaml::PARSE_CONSTANT" flag to the parser? at line 5 (near "aun_case: !php/const Drupal\auto_username\AutoUsernamePunctuationOptions::CASE_LEAVE_AS_IS") in Drupal\Core\Config\FileStorage->read() (line 118 of /var/www/lc.cx/web/core/lib/Drupal/Core/Config/FileStorage.php).

Set aun_case: 0 in auto_username.settings.yml fixed the issue.

Switch to major since this module cannot be installed.

Set aun_case: 0 in auto_username.settings.yml fixed the issue for me too.

Thanks @adiatis @Jibus

rebased branch from latest 8.x-1.x, so now MR can be merged

Cannot install the module without this patch on Drupal 10.3.6.

Thank you.

Bumped into this one, too and the fix indeed solves it.
+1 for RTBC.

In the meantime, a bump for this fix to be merged in the next stable release.

Thank you for #9!

Do we not still need the fix in the merge request?

@Liam morland. The value is set to zero in the yml file, while the original string is retained as a comment that can be reinstated when the core issue lands.

Automatically closed - issue fixed for 2 weeks with no activity.