Issue 175793004: Option to disable Angular in Dart-based Analyzer.

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

Issue 175793004: Option to disable Angular in Dart-based Analyzer. (Closed)

Created:
6 years, 10 months ago by scheglov

Modified:
6 years, 9 months ago

Reviewers:
Brian Wilkerson, blois

CC:
reviews_dartlang.org, Bob Nystrom

Base URL:
https://dart.googlecode.com/svn/branches/bleeding_edge/dart

Visibility:
Public.

More Reviews

Description

Option to disable Angular in Dart-based Analyzer. R=brianwilkerson@google.com BUG= Committed: https://code.google.com/p/dart/source/detail?r=32936

Patch Set 1 #

Created: 6 years, 10 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+54 lines, -32 lines)			Patch
	M	pkg/analyzer/lib/src/generated/engine.dart	View		7 chunks	+53 lines, -31 lines	0 comments	Download
	M	pkg/analyzer/pubspec.yaml	View		1 chunk	+1 line, -1 line	0 comments	Download

Messages

Total messages: 4 (0 generated)

Expand Messages | Collapse Messages

scheglov

Committed patchset #1 manually as r32936 (presubmit successful).

6 years, 10 months ago (2014-02-21 22:32:32 UTC) #3

blois

6 years, 9 months ago (2014-03-03 22:42:36 UTC) #4

Message was sent while issue was closed.

Curious if there was a reason this needed to go to stable here, rather than just
a dev release?

You can publish -dev versions if desired, this is what we're using for other
packages where we want to make the changes available for bleeding edge users
while accumulating more breaking changes.

Not to harp on this too much, but every version change fragments the ecosystem
of packages depending on Analyzer, and we're starting to use this in a number of
places.

Expand Messages | Collapse Messages