pkg/http/CHANGELOG.md - Issue 218623008: pkg/http v0.10.0

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: pkg/http/CHANGELOG.md

Issue 218623008: pkg/http v0.10.0 (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart

Patch Set: Created 6 years, 8 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

OLD	NEW
	1 # Changelog - http
	nweiz 2014/03/31 20:05:39 This is redundant. The changelog is primarily visi This is redundant. The changelog is primarily visible on pub.dartlang.org, and that already has headers that provide this information.
	2

1 ## 0.10.0	3 ## 0.10.0

2	4

3 * Make `BaseRequest.contentLength` and `BaseResponse.contentLength` use `null`	5 * BREAKING Make `BaseRequest.contentLength` and `BaseResponse.contentLength` use `null`
	nweiz 2014/03/31 20:05:39 Is there a style guide for changelogs? If we're go Is there a style guide for changelogs? If we're going to enforce things like annotating breaking change declarations, it would be nice to have a place where those conventions are documented.
4 to indicate an unknown content length rather than -1.	6 to indicate an unknown content length rather than -1.

5	7 * BREAKING The `contentLength` parameter to `new BaseResponse` is now named rather than
	nweiz 2014/03/31 20:05:39 Long lines. Long lines.
6 * The `contentLength` parameter to `new BaseResponse` is now named rather than

7 positional.	8 positional.

8
nweiz 2014/03/31 20:05:39 I don't understand why you're changing my formatti I don't understand why you're changing my formatting here. It makes it much harder to read. kevmoo 2014/03/31 20:17:21 Not when it goes through the markdown parser. GitH Show quoted text On 2014/03/31 20:05:39, nweiz wrote: > I don't understand why you're changing my formatting here. It makes it much > harder to read. Not when it goes through the markdown parser. GitHub breaks these into separate lists. nweiz 2014/03/31 20:29:37 That's not true: https://gist.github.com/nex3/94b9 Show quoted text On 2014/03/31 20:17:21, kevmoo wrote: > On 2014/03/31 20:05:39, nweiz wrote: > > I don't understand why you're changing my formatting here. It makes it much > > harder to read. > > Not when it goes through the markdown parser. GitHub breaks these into separate > lists. That's not true: https://gist.github.com/nex3/94b9bb285068895aabde
9 * Make request headers case-insensitive.	9 * Make request headers case-insensitive.

OLD	NEW

« no previous file with comments | « no previous file | pkg/http/pubspec.yaml » ('j') | no next file with comments »