Me again :)

I m just trying to implement e2e tests and I run into this error :

 FAIL  test/app.e2e-spec.ts
  ● Test suite failed to run

    Cannot find module 'morpheus4j/nest' from '../src/app.module.ts'

    Require stack:
      /{path}/project-name/src/app.module.ts
      app.e2e-spec.ts

      2 | import { AppController } from './app.controller';
      3 | import { AppService } from './app.service';
    > 4 | import { MorpheusModule } from 'morpheus4j/nest';
        | ^

Do you have any idea where it can come from ? I can provide a repo with this error reproducted, or just do :

nest new project-test
cd project-test
npm install morpheus4j
# set MorpheusModule module
npm run test:e2e

First, thank for the lib :)

When I am trying to run this script, mixing Write and Schema modifications :

// neo4j/migrations/V1_0_0_first migration.cypher
CREATE CONSTRAINT username_is_uniq IF NOT EXISTS FOR (user:User) REQUIRE user.username IS UNIQUE;
CREATE (u:User {username:"user 01",id:"randomUUID()",createdAt:"localdatetime()"});

It returns this error :

Tried to execute Write query after executing Schema modification

It seems to come from the prepareAndMigrateFile function, using the same transaction for each statement. I tried to use create a new transaction for each statement and it worked well.

Hey, First of, thanks for the tool. I have followed the instructions and created the morpheus config in forRoorAsync. Then my Nest app starts and tries to run migrations, which is expected. It also creates the __Neo4jMigration node of version BASELINE which is also expected. However, I can't create migrations with npm run morpheus init because it says that there is no .morpheus.json but I don't need .morpheus.json because I already have my config in main.ts. Also, if I try to create the migration manually in src/neo4j/migrations such as src/neo4j/migrations/V1_0_0__test.cypher it still says "Database up to date" when starting without performing the migrations. I ve gone through the code in the repo and I still seem unable to do it. Any advices?

In essence, the whole batch of changes included:

• Somewhat standardized migrations name (V1_2_3__name.cypher)
• Replaces id with version in the migration nodes
• Do a path matching instead of <= id
• Allows for arbitrary named verions
• Uses an actual date in the time of migrations
• Recording of the duration a single migration took
• Use the same checksum algorithm as neo4j-migrations

I locally ensured that morpheues can read neo4j-migrations and vice versa:

• Include Michael's changes
• Bump Dev dependencies
• Updated readme
• Increment test coverage. There's still work to be done.

Be aware: these changes will BREAK Morpheus version 1.

• Include Michael's changes
• Bump Dev dependencies
• Updated readme
• Increment test coverage. There's still work to be done.

Be aware: these changes will BREAK Morpheus version 1.

This changes a couple of things and I can understand if you don't want this. Also, I haven't run the tests, I'm happy that I made npm and typescript work. I was able to migrate things with your tools and verify with mine and vice versa. Key point here is using the same hashing as well as not using numeric version ids. Also, I fixed the date (should be a real date) Also, I added the duration.

I think both of our projects would benefit if interoperable. In mine, I would need to adapt to slightly different Cypher file names. However, I do thing the "VID__name.cypher" has a well established tradition inside database refactoring.

If you don't want it as a whole, pick what you like :)

• Allows for migrations having the naming V1_2_3__name.cypher
• Replaces „id“ with „version“ in the migration nodes
• Do a path matching instead of <= id
• Allows for arbitrary named verions
• Uses an actual date in the time of migrations
• records he migrations
• uses crc32 hashing of the files