-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Fix path.remove() leading & trailing comments sharing #5504
Conversation
dmail
commented
Mar 19, 2017
•
edited
Loading
edited
Q | A |
---|---|
Patch: Bug Fix? | yes |
Major: Breaking Change? | no |
Minor: New Feature? | no |
Deprecations? | no |
Spec Compliancy? | |
Tests Added/Pass? | yes/yes |
Fixed Tickets | Fixes #5503 |
License | MIT |
Doc PR | no |
Dependency Changes | no |
It will be used to preserve comment ordering when a node is removed
@dmail, thanks for your PR! By analyzing the history of the files in this pull request, we identified @hzoo and @existentialism to be potential reviewers. |
Hey @dmail! It looks like one or more of your builds have failed. I've copied the relevant info below to save you some time. |
Hey @dmail! It looks like one or more of your builds have failed. I've copied the relevant info below to save you some time. |
Hey @dmail! It looks like one or more of your builds have failed. I've copied the relevant info below to save you some time. |
Codecov Report
@@ Coverage Diff @@
## 7.0 #5504 +/- ##
==========================================
+ Coverage 85.31% 85.43% +0.12%
==========================================
Files 200 200
Lines 9490 9512 +22
Branches 2696 2702 +6
==========================================
+ Hits 8096 8127 +31
+ Misses 894 886 -8
+ Partials 500 499 -1
Continue to review full report at Codecov.
|
Will make codecov happier and there is no need for that flag anyway
Hey @dmail! It looks like one or more of your builds have failed. I've copied the relevant info below to save you some time. |
When the node has no siblings its comments must be shared with its parent. I'll add test in next commit.
Sorry for the commits noise. This pull request is still missing specific tests. |
Hey @dmail! It looks like one or more of your builds have failed. I've copied the relevant info below to save you some time. |
Hey @dmail! It looks like one or more of your builds have failed. I've copied the relevant info below to save you some time. |
I won't commit more now all checks are passing. At the moment, this pull request prevents comments order being messed up when using I cannot go further because of how comments are stored in the tree. I mean Let me know if this pull request helps you, |
Yeah we may have to redo comments based on how eslint/prettier are handling them |
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.
looks good,
Made dmail-fork#1 for fixture tests instead of js
use fixture tests
Warning : Travis says tests are passing but I'm noticing that your comments/attachment/expected.js are expecting correct comment outputs. For instance you're expecting hasPrev;
/* top */
/* left */willRemove;/* right */
/* bottom */ To become hasPrev;
/* top */
/* left */ /* right */
/* bottom */ However the current output is hasPrev; /* top */ /* left */ /* right */ /* bottom */ |
@dmail it works locally for me (both make test-only and TEST_ONLY) oh I had the same problem originally: it's because if you just npm install it installs the old version rather than the version of babel-traverse that's linked. If you |
Truly awesome work @dmail! thanks 👏 |