New Cypher Editor 1.0.0 now released #365
Merged
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
note this required re-creating the yarn lock :-/
nielsdejong
approved these changes
Mar 6, 2023
Merged
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.
We officially released the new cypher editor today, so this PR reflects that.
I hit an interesting issue with
yarnwhere the following caused issues:The resulting lock file had two copies of a bunch of packages including "@codemirror/state". This broke things, and the only way I could fix it was to delete the
yarn.lockfile and re-create it from scratch :-/.It seems that newer versions of yarn (> 1.x) automatically de-dupe packages during install so it might be worth it to think of upgrading yarn...