Skip to content

have a travis bot build and verify the docs for AngularDart per commit #1393

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
devoncarew opened this issue May 3, 2017 · 2 comments
Closed
Labels
P2 A bug or feature request we're likely to work on type-infra A repository infrastructure change or enhancement

Comments

@devoncarew
Copy link
Member

devoncarew commented May 3, 2017

We'd like to have a bot build and test the angulardart docs on every commit. We have something like this for Flutter already (https://github.com/dart-lang/dartdoc/blob/master/.travis.yml#L9, https://github.com/dart-lang/dartdoc/blob/master/tool/travis.sh#L22), but would like the same for AngularDart so we know when it breaks.

@chalin, is this something you could help with? I'm not clear how how best to gen the docs for angular. For flutter, we clone their repo and run their doc gen script (which also contains some validation code).

@devoncarew devoncarew added the type-infra A repository infrastructure change or enhancement label May 3, 2017
@chalin
Copy link
Contributor

chalin commented May 4, 2017

I'd be glad to help.

how best to gen the docs for angular. For flutter, we clone their repo and run their doc gen script (which also contains some validation code).

Might you want to use a variant of the webdev .travis.yml? The build task (line 18), is used to build and validate the docs (line 53).

The build task builds:

  • angular2 API docs (using dartdoc)
  • angular_component API docs (using dartdoc), and finally
  • the webdev site

The get-ng-repo.sh script (invoked at line 41), fetches the other repos as necessary.

cc @kwalrath

@srawlins
Copy link
Member

This has been de-prioritized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 A bug or feature request we're likely to work on type-infra A repository infrastructure change or enhancement
Projects
None yet
Development

No branches or pull requests

4 participants