Migration: handle deprecated features in migrators
Right now when one wants to remove an attribute of a meta-model or to change its name, former models would not parse anymore.
The solution would be to actually allow unknown features and then handle them manually in the migrator.
#1 Updated by Anonymous over 6 years ago
- % Done changed from 0 to 100
Done. Made an example by renaming the TableSpecification feature "samplified" into "simplified" and removing the deprecated "isSamplified" feature.
Only tricky thing to remember: now models are even silently loaded if they have some unknown features (i.e., unknown even from the migrators). Only an exception will be logged but the EMF thing will still try hard to get a model out of it. Maybe we should display a warning to the user?