Angular doc-gen reboot#14097
Conversation
IgorMinar
left a comment
There was a problem hiding this comment.
otherwise lgtm. let's merge this and we can move things later if we need to. let's keep /angular.io directory just for the app.
There was a problem hiding this comment.
this should likely be part of travis and not circle, circle is used just for linting
|
one more thing - we no longer use "chore" scopes. Please use "build(aio)" instead. More info: #14098 |
9752378 to
8120417
Compare
|
@petebacondarwin is this good to go? if so, please remove the cleanup and wip labels and add "pr: merge" label. thanks. I also suggest you rebase. |
8120417 to
68a6efb
Compare
|
rebased and ready to merge |
There was a problem hiding this comment.
Nit: Could possibly be simlified as:
return Observable.fromPromise(this.ready)There was a problem hiding this comment.
My RxJS foo is still growing but I think you are right if you mean:
search(query: string) {
return Observable.fromPromise(this.ready)
.switchMap(() => this._createQuery(query));
}There was a problem hiding this comment.
Is this (and similar statements) left intentionally?
There was a problem hiding this comment.
as I said, it was POC ... that is merged into angular/angular master!!
The `@selector` tags are not valid. Dgeni should be able to extract this information from the directive annotation metadata.
68a6efb to
9bda4c5
Compare
|
I have fixed up @gkalpak's comments and it is now again ready for merge |
The `@selector` tags are not valid. Dgeni should be able to extract this information from the directive annotation metadata.
|
landed as 1e729d7...b141a22 - I rewrote a few commit messages to follow the new guidelines (the automated check is temporarily disabled so the PR didn't fail) |
The `@selector` tags are not valid. Dgeni should be able to extract this information from the directive annotation metadata.
The `@selector` tags are not valid. Dgeni should be able to extract this information from the directive annotation metadata.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
No description provided.