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

Emit warnings when deprecated elements are found in migration steps #197

Open
gggeek opened this issue Apr 2, 2019 · 3 comments
Open

Emit warnings when deprecated elements are found in migration steps #197

gggeek opened this issue Apr 2, 2019 · 3 comments
Milestone

Comments

@gggeek
Copy link
Member

gggeek commented Apr 2, 2019

It would be a sensible strategy to start warning end users which keep using elements that will be dropped at some point in time in the future...
We probably have to find a good way for emitting the warnings though (via logger? to stderr?)

@gggeek gggeek added this to the 5.10 milestone Apr 11, 2019
@gggeek
Copy link
Member Author

gggeek commented Apr 16, 2019

Depends most likely on #201

@gggeek gggeek modified the milestones: 5.10, 5.11 Jul 15, 2019
@gggeek gggeek modified the milestones: 5.12, 5.13 Aug 10, 2020
@gggeek
Copy link
Member Author

gggeek commented Nov 3, 2020

I'd go for having warnings emitted to both Sf log and stdout (the later of course only when migrations are run from the cli)

@gggeek gggeek modified the milestones: 5.14, 5.15 Nov 22, 2020
@gggeek
Copy link
Member Author

gggeek commented Nov 30, 2020

Wondering if this is actually useful, given that:

  • the next 'major' version of this (aka TanoConsulting/eZMigrationBundle2) will have a vastly different, incompatible yml migration definition dsl
  • there are atm no plans to evolve this 'branch' to new versions which actually drop support for deprecated yml syntax...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant