Velocity
Velocity copied to clipboard
Improved configuration version handling
Currently the user is "forced" to handle the configuration update on their own, deleting the configuration they have in place to add the new options, whereas the job should be handled by Velocity, especially with a patch version being developed 3.1.2
.
This pull request replaces the old logic for handling version 1.0 and 2.0 configuration to a single migration. This would also allow more migrations to be done in case more configuration options or changes are added in the future, e.g. #666. Possibly resolves #733 , but only for the new options that may be added from now on
Collides with #772 Please either wait and rebase or target the PR branch so we can pull this later.
superseded by #1111