-
Notifications
You must be signed in to change notification settings - Fork 44
ddc investigation #327
Comments
Here's the current breakdown of ddc reported issues (~83 right now). I haven't looked into these too closely. Note that the output of the cli tool is pretty hard to parse - |
Scratch the |
I looked at the ones in https://codereview.chromium.org/1353873002/ I filed an issue on the best fix for |
An update - we went from 85 errors to 55, with fixes to collection, markdown, and pub_semver. Here's the latest when run on
There are PRs outstanding for frape and stream_transformers to fix a few more issues. I spot checked |
Also cc @kevmoo; we're working through package: issues with ddc. |
I'm happy to take a look at YAML, unless someone else is already. |
@devoncarew Please put check-boxes in this issue and assign sub-issues to packages. |
(moved to the top) |
I think if you put the checkboxes in the first message (by editing it) it will do a neat UI thing showing % complete. |
FYI @vsmenon ... we have a problem here in that we are analyzing against the user's SDK, which itself has strong mode errors. For example, one of the YAML errors is caused by |
the error is:
|
@jmesserly - the Map issue was fixed by Lasse's SDK change, right? |
yes. |
Perhaps ddc should emit a warning if it's analyzing against an sdk that's older than one with some required fixes? Or, bump up the sdk constraint in its pubspec? The 2nd option is simpler but means that users might be running against older versions of ddc w/o realizing it. |
yeah we can totally bump the pubspec as soon as we have a dev build. I think that's probably fine, since Pub will show you that you didn't get the latest DDC version. For what it's worth, we have a way more serious SDK problem at the moment :) |
Some |
Just 23 left! It's down to
|
Nice! The very last one was already fixed in the SDK (MapMixin.containsValue) - should disappear when running against the next release. |
By the way, you probably want to set |
Should this be the default then? I wasn't aware of the option, or that you'd most likely want to run with it on. I'm seeing 294 issues w/ that flag in the plugin, up from 24. |
And, thanks for the info - good to know! |
yes. I was really surprised it is not... |
Re: https://codereview.chromium.org/1374563004/ - thanks! |
See dart-atom/dart#327 R=vsm@google.com Review URL: https://codereview.chromium.org/1374563004 .
Doing some bug triage - the initial investigation is done; this issue largely covered making things strong mode compliant. |
See dart-atom/dart#327 R=vsm@google.com Review URL: https://codereview.chromium.org/1374563004 .
package:collection
happy (issue filed here: Support B <: A<bottom> dart-archive/dev_compiler#324)package:frappe
happy (email out to author re: reviewing PRs)package:stream_transformers
happy (Fix type problems danschultz/stream_transformers#23, update the travis build danschultz/stream_transformers#24)package:yaml
happy (dart-lang/yaml#15.)(redacted to get the checkmarks in the first comment)
The text was updated successfully, but these errors were encountered: