Skip to content
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

docs(aio): update headers for toc #16969

Merged
merged 1 commit into from
May 26, 2017
Merged

Conversation

Foxandxss
Copy link
Member

Verified that there are no weird "entry" in the ToC, removed all the commented out toc (now that I verified that they are nice) and changed the @title to h1 (#) continuing Ward's work.

@@ -781,7 +774,7 @@ Here again are the TypeScript entry-point files that define the `polyfills` and

{@a highlights}

### Highlights
## Highlights
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure about this, but happy with it if you are.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In fact, you are right about this one. Not sure what was I thinking about. Or even noToc for this one.

@@ -3862,7 +3751,7 @@ drop the `canLoad` guard and rely on the [CanActivate](guide/router#can-activate
Preloading every lazy loaded modules works well in many situations,
but it isn't always the right choice, especially on mobile devices and over low bandwidth connections.
You may choose to preload only certain feature modules, based on user metrics and other business and technical factors.

rm
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

???

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is called: Multiple monitors and not being sure where your focus is at

@@ -550,7 +486,8 @@ from components outside the `AppComponent` tree. This is a rare use case.

More generally, [prefer registering providers in modules](guide/ngmodule-faq#q-component-or-module) to registering in components.

### Discussion
<h3 class="noToc">Discussion</h3>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

noToc will work, but no-toc is what we use in most places 😃
That said, why no ToC?

Learn how to use ahead-of-time compilation.

@description
# Ahead-of-Time Compilation

This cookbook describes how to radically improve performance by compiling _ahead-of-time_ (AOT)
during a build process.

{@a toc}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove?

@@ -136,7 +124,7 @@ Now when the app runs, the `myHighlight` directive highlights the paragraph text

<div class="l-sub-section">

### Your directive isn't working?
<h3 class="noToc">Your directive isn't working?</h3>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

noToc will work, but we use no-toc in most places 😁

@Foxandxss
Copy link
Member Author

Fixed concerns.

@gkalpak
Copy link
Member

gkalpak commented May 23, 2017

LGTM as soon as Travis is green 😁

@petebacondarwin
Copy link
Member

The errors are due to inline tags breaking for some reason. I will look into it

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@petebacondarwin petebacondarwin added this to REVIEW in docs-infra May 24, 2017
@mary-poppins
Copy link

The angular.io preview for 1053ef4 is available here.

@petebacondarwin petebacondarwin added the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label May 25, 2017
@petebacondarwin
Copy link
Member

@Foxandxss - please squash my commit into yours and then mark as merge

@petebacondarwin
Copy link
Member

@IgorMinar - can you approve the docs change to common, please.

@petebacondarwin petebacondarwin moved this from REVIEW to MERGE in docs-infra May 25, 2017
@googlebot
Copy link

CLAs look good, thanks!

@Foxandxss
Copy link
Member Author

@petebacondarwin done.

@mary-poppins
Copy link

The angular.io preview for fc6da8b is available here.

@petebacondarwin petebacondarwin added action: merge The PR is ready for merge by the caretaker and removed action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews labels May 26, 2017
@chuckjaz chuckjaz merged commit cd5bc64 into angular:master May 26, 2017
@petebacondarwin petebacondarwin removed this from MERGE in docs-infra May 26, 2017
asnowwolf pushed a commit to asnowwolf/angular that referenced this pull request Aug 11, 2017
juleskremer pushed a commit to juleskremer/angular that referenced this pull request Aug 28, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants