Meta: add .editorconfig and .gitattributes #102
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
|
A wrap is definitely what I want. I was actually going to ask on IRC if there was a norm for this as I was curious why this spec had massive run-on lines. |
domfarolino
approved these changes
Mar 27, 2017
|
Great. Let's leave wrapping as separate. If we do let's remember to add the line to editorconfig with the max line length, |
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.
Part of whatwg/meta#7.
I believe this will also instruct GitHub to wrap lines in .bs files by treating them as .html files. That should help reviewing a lot.
Alternately the spec could start wrapping at 100 characters like most WHATWG specs; not sure if that's worthwhile/what the editors want though.