Skip to content

dartdoc integration test needs to have a mode that doesn't fail on trivial doc changes #1456

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

Closed
jcollins-g opened this issue Jun 5, 2017 · 0 comments
Assignees
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures type-code-health Internal changes to our tools and workflows to make them cleaner, simpler, or more maintainable
Milestone

Comments

@jcollins-g
Copy link
Contributor

To fix the test, I suggest adding a dartdoc command line option to drop inherited text from the SDK in generated docs and replace it with a stub. This way we can still verify that dartdoc is generating the right structure and is choosing correctly when to import docs from the SDK without depending on the exact contents of those docs themselves.

I believe this is the main blocker on running our tests as part of the main suite in the SDK.

@devoncarew

@jcollins-g jcollins-g added type-code-health Internal changes to our tools and workflows to make them cleaner, simpler, or more maintainable P1 A high priority bug; for example, a single project is unusable or has many test failures labels Jun 5, 2017
@jcollins-g jcollins-g added this to the dartdoc 1.0 milestone Jun 5, 2017
@jcollins-g jcollins-g self-assigned this Jun 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures type-code-health Internal changes to our tools and workflows to make them cleaner, simpler, or more maintainable
Projects
None yet
Development

No branches or pull requests

1 participant