Skip to content

dartdoc should operate on SDK repo as well as the built SDK #1617

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.

Sign up for GitHub

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

Jump to bottom
Closed
jcollins-g opened this issue Feb 27, 2018 · 1 comment
Closed

dartdoc should operate on SDK repo as well as the built SDK #1617

jcollins-g opened this issue Feb 27, 2018 · 1 comment
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures type-enhancement A request for a change that isn't a bug

Comments

@jcollins-g
Copy link
Contributor

It would really reduce iteration time for modifying docs in the SDK if you didn't have to build and install it before rendering docs.

@kwalrath
@jcollins-g jcollins-g added type-enhancement A request for a change that isn't a bug P2 A bug or feature request we're likely to work on labels Feb 27, 2018
@jcollins-g jcollins-g added P1 A high priority bug; for example, a single project is unusable or has many test failures and removed P2 A bug or feature request we're likely to work on labels Mar 27, 2018
@jcollins-g
Copy link
Contributor Author

jcollins-g commented Mar 27, 2018 •
edited
Loading

Increasing this to P1. Triage priorities say if there's evidence there's a big win enhancements should be P1, and I think that's true in this case. It is really, really slow to iterate on docs right now in the SDK.

This was referenced Apr 10, 2018
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures type-enhancement A request for a change that isn't a bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jcollins-g