yworks / migrate-yfiles-app Goto Github PK

Currently only fully qualified class names are automatically renamed. Since there is only one rename from 2.2 to 2.3 this is not that critical, but nevertheless we should rename the imports, too.

The migration tool fails when parsing a file that contains require(foo)

We always use tsx extensions, but it won't let me do that? This is a bug.

Instead of globally installing the tool, using npx would allow users to always use the latest version without having to pollute their "global" node modules.

When the directory in which the tool is executed contains a babel.config.js file, you will get all kind of weird errors in the globally installed migration tool npm files... That sounds like a bug somewhere else, but is really weird and not unlikely to happen with customer code.

That would be very helpful for many users.

This should only require a "src" directory and it will not touch the files but only output the list of required changes. This is only interesting for the smaller API changes, not for the rewriting to ES6 classes, etc.

It's not really clear how this works and what directories need to be set.