You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building fields in the CP, statements in project config yaml look like this: required: false sortOrder: 1
etc.
When running a rebuild later (which should just leave the yaml alone), it always replaces original values with these: required: '0' sortOrder: '1'
etc.
This can even be seen on an empty install when using the project config as a quick start - the values switch on initial install the same way.
I'm running the config sync locally on a Windows dev environment (WinNmp - nginx, php 7.3, mysql 5.7).
This doesn't affect functionality afaik, but it makes the Git commits hard to review for actual project config changes.
Steps to reproduce
Add some fields via CP
Run ./craft project-config/rebuild
Commit project config to Git and look at changes
Additional info
Craft version: Craft Pro 3.1.20.1
PHP version: 7.3.2
Database driver & version: MySQL 5.7.21
Plugins & versions: /
The text was updated successfully, but these errors were encountered:
Thanks @jamesmacwhite , that helps. I guess I'll make sure to run a project config rebuild before every commit then as that seems to normalize everything to MySQL string values - so I can keep the useful Git commit comparisons.
For anyone else reading this - if you're developing and don't care for keeping soft deleted items, it's better to run garbage collection before rebuilding the config (or deleted sections will find themselves back in the yaml file). This issue should get resolved soon though - #4100
Description
When building fields in the CP, statements in project config yaml look like this:
required: false
sortOrder: 1
etc.
When running a rebuild later (which should just leave the yaml alone), it always replaces original values with these:
required: '0'
sortOrder: '1'
etc.
This can even be seen on an empty install when using the project config as a quick start - the values switch on initial install the same way.
I'm running the config sync locally on a Windows dev environment (WinNmp - nginx, php 7.3, mysql 5.7).
This doesn't affect functionality afaik, but it makes the Git commits hard to review for actual project config changes.
Steps to reproduce
./craft project-config/rebuild
Additional info
The text was updated successfully, but these errors were encountered: