Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] add command to forcefully sync a field in case project.yaml doesn't pick it up correctly #4126

Closed
N0ps32 opened this Issue Apr 11, 2019 · 3 comments

Comments

Projects
None yet
3 participants
@N0ps32
Copy link

commented Apr 11, 2019

I'd like to propose a craft CLI command that can be used to force-sync a project.yaml field. We sometimes run into issues where a newly added field isn't being picked up by craft. It would be really useful if you could force craft to sync those fields by specifying a field handle.

./craft force-sync <handle>

Something like that.

@andris-sevcenko

This comment has been minimized.

Copy link
Member

commented Apr 11, 2019

We’re exploring the option of forcing Craft treat every second-level entry as changed, forcing a re-save. So, yeah, sounds good to me! That should help alleviate some of the bugs left over from a mishap when syncing.

@andris-sevcenko

This comment has been minimized.

Copy link
Member

commented Apr 11, 2019

To clarify - adding an option to do that when syncing via CLI.

@andris-sevcenko

This comment has been minimized.

Copy link
Member

commented Apr 16, 2019

We've released Craft 3.1.23 with the possibility to do ./craft project-config/sync --force, which would forcibly sync the project.yaml file to already-saved entities.

It ended being unfeasible at the time to add the chance to force-sync just a single path because project config does not yet support delta updates to the serialized config.

The --force option should solve your issue, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.