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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Codemirror benchmarks #150
Codemirror benchmarks #150
Changes from 26 commits
12d2aa6
28f3c05
0784c5e
9fe4a83
9b5ae36
0e49894
2016f92
41e3f64
1b247e2
03a53c3
b6cf809
63d1650
68040ac
55cb3e1
43fcaf4
a9bae95
280ffab
cfb85dd
39c1ea3
bb8e2f9
5fc04ce
7780425
c0a3f92
daa37d8
aedbc50
19276d7
ee711cc
3e10950
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not a fan of this cause if someone had this env variable defined (unlikely but still possible) then the behaviour of the language server changes.
I'd rather probably we had a method to clean the cache and we call that after every test of the benchmark?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wdyt about naming it something where it is more obvious the behavior of the language server changes, something like:
BENCHMARK_CYPHER_LANGUAGE_SERVER
?I'm fine with having a method to clean the cache as well if you prefer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think explicitly cleaning the cache is a better idea IMO. The reason is right now I'm not sure whether this is benchmarking the right thing because in the auto-completion or the syntax validation we are also including another component, which is the parsing. So I'd rather we could control when to clean or not to clean the cache
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm flexible, so if you prefer to do that on another PR, we can iterate on this. That way we get to test it out as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it'd be nice to do in a follow up PR, just to see that the Github actions work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went ahead and did it directly in this PR instead.