pkg/path/pubspec.yaml - Issue 22284003: pkg: analysis aided cleanup

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/path/pubspec.yaml

Issue 22284003: pkg: analysis aided cleanup (Closed) Base URL: http://dart.googlecode.com/svn/branches/bleeding_edge/dart

Patch Set: Created 7 years, 4 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:

OLD	NEW
1 name: path	1 name: path

2 author: "Dart Team <misc@dartlang.org>"	2 author: Dart Team <misc@dartlang.org>

3 homepage: http://www.dartlang.org

4 documentation: http://api.dartlang.org/docs/pkg/path

5 description: >	3 description: >

6 A string-based path manipulation library. All of the path operations you know	4 A string-based path manipulation library. All of the path operations you know

7 and love, with solid support on both Windows and POSIX (Linux and Mac OS X)	5 and love, with solid support on both Windows and POSIX (Linux and Mac OS X)

8 machines.	6 machines.

	7 homepage: http://www.dartlang.org

	8 documentation: http://api.dartlang.org/docs/pkg/path

	9 dev_dependencies:

	10 unittest: any
	gram 2013/08/05 23:23:12 Do we need this unittest dependency here? I'm not Do we need this unittest dependency here? I'm not sure what the right convention should be. Personally I favor putting a pubspec with a unittest dependency in the test directory, and not having it in the main package directory; that means you can open up the test directory in the editor and run the tests after a pub install, and if you're just using a package and not testing it you don't need the dependency here. Bob, Nathan, do you have an opinion here? Should unittest go in as a dependency of all pub packages with tests in their top-level pubspecs?
OLD	NEW