Closed maxime-rainville closed 3 months ago
Should the task be enabled or disabled by default? I'd recommend disabled by default so it's not present for new installations. Developers who are migrating can enable it with a simple yaml config, run it, and disable it again afterward.
Bear in mind this is one of three migration tasks, and only one of these will apply to any given project, so probably makes sense to not show them all by default.
My assumption was be that this task would a dev/build
task. You would have to explicitly choose to run the task by calling it. This would seem to negate the need to have the option to enable/disable it.
Did you have something else in mind?
As a developer maintaining a project using LinkField v2/v3, I have a a clear path and clear guidance on how to migrate to v4.
Acceptance criteria
BuildTask
exists to converts LinkField v2/v3 data to v4 format.Deprecation warnings are added to v3.see https://github.com/silverstripe/silverstripe-linkfield/issues/246@deprecated
.Exclude
Possible unusual v3 customisations
PRs
See this installer run for green CI with the combined PRs.