Summary

Update the spec to include the line_endings option and trailing newline rules.

Review Request #11768 — Created Aug. 2, 2021 and submitted Aug. 4, 2021, 3:03 p.m.

Information

Owner

chipx86

Repository

DiffX

Branch

master

Bugs

Depends On

Reviewers

Groups

diffx

People

Description

This introduces a new content option, line_endings, which is used to
define the explicit type of line endings the content uses. This is
primarily important for diff content, due to real-world encounters with
diffs that only appear to be in one form of line ending or another.

Along with this, information on content sections now explicitly state
that the section must end in a newline in the section's encoding.

Testing Done

Built the docs and read through them. Checked that term links were
worked correctly. Checked for spelling errors.

Commits

Summary	ID
Update the spec to include the line_endings option and trailing newline rules. This introduces a new content option, `line_endings`, which is used to define the explicit type of line endings the content uses. This is primarily important for diff content, due to real-world encounters with diffs that only appear to be in one form of line ending or another. Along with this, information on content sections now explicitly state that the section must end in a newline in the section's encoding.	2bf18a15e1b640e1421506a3f90d57ac3536a2e4

Summary

Update the spec to include the line_endings option and trailing newline rules.

This introduces a new content option, `line_endings`, which is used to define the explicit type of line endings the content uses. This is primarily important for diff content, due to real-world encounters with diffs that only appear to be in one form of line ending or another. Along with this, information on content sections now explicitly state that the section must end in a newline in the section's encoding.

2bf18a15e1b640e1421506a3f90d57ac3536a2e4

Issues

Description	From	Last Updated
noted handled?	david	Aug. 3, 2021, 9:15 p.m.

flake8 passed.

JSHint passed.

Change Summary:

Made the CRCRLF line ending example explicit (showing \r\r\n).

Commits:

	Summary	ID
	Update the spec to include the line_endings option and trailing newline rules. This introduces a new content option, `line_endings`, which is used to define the explicit type of line endings the content uses. This is primarily important for diff content, due to real-world encounters with diffs that only appear to be in one form of line ending or another. Along with this, information on content sections now explicitly state that the section must end in a newline in the section's encoding.	9d23ecd3de5f435856cf57ab0db03fd79b8f6845
	Update the spec to include the line_endings option and trailing newline rules. This introduces a new content option, `line_endings`, which is used to define the explicit type of line endings the content uses. This is primarily important for diff content, due to real-world encounters with diffs that only appear to be in one form of line ending or another. Along with this, information on content sections now explicitly state that the section must end in a newline in the section's encoding.	61544c6635a2e0ff2dc0d809d6c6b114b5915305

Diff:

Revision 2 (+104 -2)

Show changes

	docs/glossary.rst
	docs/spec/section-format.rst
	docs/spec/sections.rst

Checks run (2 succeeded)

flake8 passed.

JSHint passed.

docs/spec/section-format.rst (Diff revision 2)
The issue has been resolved. Show all issues
```
noted handled?
```
1. chipx86 Aug. 3, 2021, 1:21 a.m.
  "noted handled", short for "noted handled a to teh fix it"

Change Summary:

Removed an unintentional word in a description.

Commits:

	Summary	ID
	Update the spec to include the line_endings option and trailing newline rules. This introduces a new content option, `line_endings`, which is used to define the explicit type of line endings the content uses. This is primarily important for diff content, due to real-world encounters with diffs that only appear to be in one form of line ending or another. Along with this, information on content sections now explicitly state that the section must end in a newline in the section's encoding.	61544c6635a2e0ff2dc0d809d6c6b114b5915305
	Update the spec to include the line_endings option and trailing newline rules. This introduces a new content option, `line_endings`, which is used to define the explicit type of line endings the content uses. This is primarily important for diff content, due to real-world encounters with diffs that only appear to be in one form of line ending or another. Along with this, information on content sections now explicitly state that the section must end in a newline in the section's encoding.	2bf18a15e1b640e1421506a3f90d57ac3536a2e4

Diff:

Revision 3 (+104 -2)

Show changes

	docs/glossary.rst
	docs/spec/section-format.rst
	docs/spec/sections.rst

Checks run (2 succeeded)

flake8 passed.

JSHint passed.

Ship it!

```
Ship It!
```

Status:: Completed
Change Summary:: Pushed to master (cb4445b)