You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Push API specification is a large mixture of spaces, tabs, different forms of indentation (4 spaces in WebIDL, 1 space in example code), has carriage returns, and so on.
While I by no means intend to kick off another tabs vs. spaces discussion, it would be nice if we could agree on what (I believe) to be the frequent preference for specifications: spaces for indentation, no tabs, use new-lines for line breaks, no carriage returns. WebIDL to be indented 4 spaces, example code to be indented 2 spaces.
The text was updated successfully, but these errors were encountered:
Issue originally posted by @beverloo at
telefonicaid/WebAPISpecs#28
The Push API specification is a large mixture of spaces, tabs, different forms of indentation (4 spaces in WebIDL, 1 space in example code), has carriage returns, and so on.
While I by no means intend to kick off another tabs vs. spaces discussion, it would be nice if we could agree on what (I believe) to be the frequent preference for specifications: spaces for indentation, no tabs, use new-lines for line breaks, no carriage returns. WebIDL to be indented 4 spaces, example code to be indented 2 spaces.
The text was updated successfully, but these errors were encountered: