-
Notifications
You must be signed in to change notification settings - Fork 156
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] number of small corrections to the specification #98
Conversation
…er 2 examples are correct afaik.
… it following at the end after some external links
… merged with the main spect (right now only meg, but eeg and ieeg are coming)
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 ain't a complete review, but a few notes how to make PR better ;)
THANK YOU btw -- we should indeed polish up the spec so there is no place for ambiguity and errors like the ones you (and now me ;-) ) point out!
Thanks for sending this along, FYI - here are the linter errors Travis spotted: https://travis-ci.com/bids-standard/bids-specification/builds/92812807 |
FWIW +1 on formalizing to use American English, and mention that in common principles of it isn't there yet |
Contributors guide would be a better place to put such recommendation.
…On Thu, Nov 29, 2018, 5:41 AM Yaroslav Halchenko ***@***.*** wrote:
FWIW +1 on formalizing to use American English, and mention that in common
principles of it isn't there yet
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOkp_ayZf7GtHdknkOJh-iTjl6IaZ9pks5uz-QFgaJpZM4Y3Hqq>
.
|
@robertoostenveld would you have time to resolve outstanding issues causing CIs to fail? I think we are ready otherwise and should merge! |
@robertoostenveld - I have pushed a commit resolving introduced problems. If would be all kosher - I would merge or we would be in jeopardy to introduce conflicts |
…n favor of the master/HEAD
The Christmas period delayed work on this. I have updated to the HEAD of the master branch and resolved the conflicts. I see that circleci passes, but that travis fails: I will investigate. |
… small cleanup to the extensions page.
8316552
to
7d1bb72
Compare
Whereas travis initially was showing "Incorrect list-item indent: add 2 spaces", after me changing it it to 2 spaces it was showing "Incorrect list-item indent: add 1 space". Also the table fence around the emojis seems impossible to get right. I am lost! Content wise it all seems fine to me, so I suggest to merge. |
Consider using https://github.com/prettier/prettier to automatically fix syntax |
... so I managed to get all checks to pass! @chrisfilo: the opinion of Furthermore, remark-lint gives me |
I agree, but this is a good topic for a new issue (perhaps proposing less strict linting). |
@yarikoptic @robertoostenveld is this read to merge? |
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 to me ... except for in the contributors file, where a line seems to be removed: If you can tell me why (or fix this "typo"), I can approve and merge this.
Added missing contributor back
this is ready to merge. |
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 to me. Thanks!
@yarikoptic thanks. This is minor, but please wait 5 days since the last commit before merging next time (as per https://github.com/bids-standard/bids-specification/blob/master/DECISION-MAKING.md#rules). At least until someone automates this (see #147). |
Ok, noted |
These are mostly formatting changes and fixes to external links.