refactor: Make compatible with neo4j-migrations. #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
|
Thank you so much for your contribution! |
Merged
|
🎉 This PR is included in version 1.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Merged
marianozunino
added a commit
that referenced
this pull request
Feb 21, 2022
* chore: add eslint rule * refactor: create repository Created a repository to facilitate testing * chore: add build status badge * test(repository): wip * refactor: move tests files to test dir * fix: test cov output directory * test: unit test neo4j * refactor!: Make compatible with neo4j-migrations. (#6) 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 * refactor: rename type Neo4jMigration to Neo4jMigrationNode * test: increment utils coverage * test: increment repository coverage * chore: update readme * chore: update dev dependencies Co-authored-by: Michael Simons <michael@simons.ac>
marianozunino
added a commit
that referenced
this pull request
Feb 21, 2022
* chore: add eslint rule * refactor: create repository Created a repository to facilitate testing * chore: add build status badge * test(repository): wip * refactor: move tests files to test dir * fix: test cov output directory * test: unit test neo4j * refactor: Make compatible with neo4j-migrations. (#6) BREAKING CHANGE: 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 * refactor: rename type Neo4jMigration to Neo4jMigrationNode * test: increment utils coverage * test: increment repository coverage * chore: update readme * chore: update dev dependencies Co-authored-by: Michael Simons <michael@simons.ac>
marianozunino
added a commit
that referenced
this pull request
Feb 21, 2022
* chore: add eslint rule * refactor: create repository Created a repository to facilitate testing * chore: add build status badge * test(repository): wip * refactor: move tests files to test dir * fix: test cov output directory * test: unit test neo4j * refactor: Make compatible with neo4j-migrations. (#6) BREAKING CHANGE: 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 * refactor: rename type Neo4jMigration to Neo4jMigrationNode * test: increment utils coverage * test: increment repository coverage * chore: update readme * chore: update dev dependencies Co-authored-by: Michael Simons <michael@simons.ac>
github-actions bot
pushed a commit
that referenced
this pull request
Feb 21, 2022
# [2.0.0](v1.0.0...v2.0.0) (2022-02-21) ### Features * release ([#9](#9)) ([b63e988](b63e988)), closes [#6](#6) ### BREAKING CHANGES * 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 * refactor: rename type Neo4jMigration to Neo4jMigrationNode * test: increment utils coverage * test: increment repository coverage * chore: update readme * chore: update dev dependencies Co-authored-by: Michael Simons <michael@simons.ac>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In essence, the whole batch of changes included:
V1_2_3__name.cypher)idwithversionin the migration nodesI locally ensured that morpheues can read neo4j-migrations and vice
versa: