Skip to content
New issue

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

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

Already on GitHub? # to your account

Future enhancements to migration #35

Open
artgoldberg opened this issue Feb 5, 2019 · 1 comment
Open

Future enhancements to migration #35

artgoldberg opened this issue Feb 5, 2019 · 1 comment

Comments

@artgoldberg
Copy link
Contributor

artgoldberg commented Feb 5, 2019

Listed in decreasing order of my subjective assessment of importance

  1. avoid need for obj_model.core.ModelMeta.CHECK_SAME_RELATED_ATTRIBUTE_NAME by comparing related models by value, not name
  2. use Model.revision to label git commit of wc_lang and automatically migrate models to current schema and report inconsistency between a schema and model file
  3. move generate_wc_lang_migrator() to wc_lang
  4. provide a well-documented example
  5. YAML config examples with multiple existing_files and multiple migrated_files
  6. use deepcopy on obj_model.ontology.OntologyAttribute attributes when deepcopy of pronto terms works
  7. associate schema pairs with renaming maps
  8. separately specified default value for attribute
  9. improve performance of test_migration
  10. obtain sort order of sheets in existing model file and replicate in migrated model file
  11. confirm migration works for json, etc.
  12. test sym links in Migrator.parse_module_path
  13. use PARSED_EXPR everywhere applicable
@jonrkarr
Copy link
Member

jonrkarr commented Jul 5, 2019

generate_wc_lang_migrator should be moved to wc_lang

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

No branches or pull requests

2 participants