-
Notifications
You must be signed in to change notification settings - Fork 125
dartdoc silently creates bad documentation when run with 2.0.0-dev.22.0 #1603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
(This is with a .packages file generated with 2.0.0-dev.22.0 -- 21 works, 22 does not). |
At least some of these test failures appear to be related to core library changes. |
One inheritance problem seems to be tests in dartdoc unintentionally depending on ListMixin not adding methods -- but it did in 22.0. Still looking at other issues. |
Enums seem to be a real issue. Dartdoc will silently drop all enum values. |
Attempting to figure out where the enum values went by stepping with the debugger landed me with this assertion:
stack trace:
|
Some code landed recently according to @scheglov in analyzer to fix this problem, but it hasn't been published yet. It may be possible to work around the flutter bug by doing the thing we should never do: use the dartdoc version in the SDK. Running in checked mode seems to work with the SDK version of dartdoc. The alternative is to publish a new analyzer and then wait for a new dartdoc before rolling to flutter. (We need to publish analyzer anyway for this, but we could unblock flutter). |
(There are good reasons not to use the dartdoc in the SDK for flutter, specifically the lack of integration testing for that version of dartdoc, noone uses it so its integration is likely to be a bit rusty -- but it is an option). |
Now working on verifying I can publish an analyzer package at top of tree, run dartdoc with it, and generate reasonable flutter docs. Tricky, because #1601 means I can't use the |
I have verified that the docs generated by the head analyzer with SDK 22.0 are reasonable. CL/PRs coming up for analyzer+kernel+front_end and dartdoc releases. |
https://dart-review.googlesource.com/c/sdk/+/40401 -- Prepare to publish analyzer |
Verified that the new analyzer at least smoke-tests on .21 still, so did not update SDK constraints. Publish is to address dart-lang/dartdoc#1603. Change-Id: I39320e5557344f6c1c79df50b792246fc1c29840 Reviewed-on: https://dart-review.googlesource.com/40401 Commit-Queue: Janice Collins <[email protected]> Reviewed-by: Brian Wilkerson <[email protected]> Reviewed-by: Devon Carew <[email protected]>
Dartdoc v0.16.0 has been published, which uses the new analyzer and addresses the issue. |
When trying to unpin dartdoc on travis, I tested it with 2.0.0-dev.22.0 SDK on Linux. This resulted in a big pile of test failures.
Running with the exact same .packages file works fine in 2.0.0-dev.21.0 -- same analyzer version, same front-end (that's being used by dartdoc), etc.
The text was updated successfully, but these errors were encountered: