When we are developing a site, we might have 3-4 versions of the site on different enviroments with different databases. This is a problem when syncing with git sence the acf settings are not theme specific, but database specific.
It would be great if the fields structure could somehow be stored with the theme so it can be commited so that the fields and theme updates can be commited and deployed together.
Maybe some kind of version of migrations like in Laravel?
I’ve used this featured but I’m not 100% satisfied with this feature. It does help with binding field logic to a theme, but it does not help with version control and local development. This feature is a one way export. Once it has been exported and transfered to another enviroment, I can not easily change or extend these settings. Also, this method doesn’t work well with merging two different setups that has been developed separatly.
Maybe an alternative option to store all, or maybe just a fieldset’s, structure as a json document (like composer) in the active theme, instead of the database.
For anyone keeping up with my @wp_acf adventure today I actually made some progress with "ACF Shortcake" that mashes together the functionality of Shortcake and ACF Field groups inside ACF WYSIWYG fields.