-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Delimiter selector updated #347
Conversation
AndreasArvidsson
commented
Nov 30, 2021
•
edited
Loading
edited
- Delimiter selector made more robust and usable for all languages
- Added a lot of language specific play/test files. They have very little in them right now but the purpose is that each language should have a file with all the common structures making it easier to test while developing.
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 like this idea. A few things
- Looks like the line endings got messed up or something? Strange diffs
- Looks like a few junk files appeared, eg
tmp.tsx
and a couple empty files. The markdown one also looks strange - Please add tests for the things you fixed
- I'd be tempted to put all the files, including hat-test, into a
data/playground
directory. I think "test" is probably a confusing name because they're not actually tests. Prob my fault for calling it "hat-test". I think I'd maybe godata/playground/hats.txt
,data/playground/typescript.ts
, etc?
Now I think everything is fixed :) |
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.
This is really nice. Left a couple minor suggestions
src/test/suite/fixtures/recorded/languages/java/chuckTypeNear.yml
Outdated
Show resolved
Hide resolved
}, | ||
); | ||
} else { | ||
trailingDelimiterRange = makeRangeFromPositions( |
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.
What if we walked up parents until we find one with a previous sibling and then ask for end of previous sibling there? Not sure it's worth the effort but might make white space a bit cleaner
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.
We can't try that
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.
Did you mean to say "we can try that?"
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 don't think we have to. So far no language has need of this with the current implementation.