-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
dart doc
fails in built SDK
#47677
Comments
The Reverting in https://dart-review.googlesource.com/c/sdk/+/220006 |
Problem diagnosis: dartdoc relies on resources for creating it's output. In a built SDK those are in a
This
When we run |
cc @bkonyi any good ideas for how to handle this? |
This reverts commit 916a43a. Reason for revert: command fails in built SDK, see #47677 Original change's description: > Initial 'dart doc' developer command > > Initial 'dart doc' command for the unified 'dart' developer tool, > over time replacing the exiting 'bin/dartdoc' tool. > > Change-Id: Ib5639f9329bf5ed86375c97c5e485471934c56ff > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/217980 > Commit-Queue: Michael Thomsen <mit@google.com> > Reviewed-by: Ben Konyi <bkonyi@google.com> # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: I5eb04c68cb80b1e2b95642e9e7904ad86c603315 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/220006 Reviewed-by: Michael Thomsen <mit@google.com> Reviewed-by: Ben Konyi <bkonyi@google.com> Commit-Queue: Michael Thomsen <mit@google.com>
We'll either need to not use |
I highly recommend not using Perhaps require the caller who starts DartDoc to pass you a URI pointing to the resource directory. Or allow it, and fall back on the default |
Yeah, the caller knows where the resource directory is, so it's pretty easy to pass that to dartdoc: I just don't know how to change dartdoc to actually read from this location, as it's code for locating resources is a bit hard for me to grok. |
Closing this issue as this was reverted in https://dart-review.googlesource.com/c/sdk/+/220006 (and thus no longer fails in The |
Repro steps:
In a bleeding edge SDK, run:
=>
The text was updated successfully, but these errors were encountered: