mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00

Joe Martin (Crowdstaffing) 42289f25c6 docs: improve markdown (#45325 )

The purpose of the changes is to clean all markdown to match a single pedantic style.

*   To ensure all changes in style are properly separated.
*   To ensure all styled content aligns to nearest 4-character-tab.
*   To ensure all code blocks use the Angular `<code-example>` or `<code-tab>` elements.
*   To ensure all markdown exists outside of html tags.
*   To ensure all images use the Angular style for `<img>` elements.
*   To ensure that all smart punctuation is replaced or removed.

    ```text
    ’, ’, “, ”, –, —, …
    ```

*   To ensure all content does not conflict with the following reserved characters.

    ```text
    @, $, *, &, #, |, <, >,
    ```

*   To ensure all content displays using html entities.

The following changes were made to files in the following directory.

```text
aio/content
```

The target files were markdown files.
The list of excluded files:

```text
.browserslistrc, .css, .conf, .editorconfig, .gitignore, .html, .js, .json, .sh, .svg, .ts, .txt, .xlf,
```

PR Close #45325

2022-04-08 19:36:30 +00:00

932 B

Raw Blame History

Debugging tests

If your tests aren't working as you expect them to, you can inspect and debug them in the browser.

Debug specs in the browser in the same way that you debug an application.

Reveal the Karma browser window. See Set up testing if you need help with this step.
Click the DEBUG button; it opens a new browser tab and re-runs the tests.
Open the browser's "Developer Tools" `Ctrl-Shift-I` on Windows; `Command-Option-I` in macOS.
Pick the "sources" section.
Open the 1st.spec.ts test file Control/Command-P, then start typing the name of the file.
Set a breakpoint in the test.
Refresh the browser, and it stops at the breakpoint.

@reviewed 2022-02-28

932 B Raw Blame History

Debugging tests

932 B

Raw Blame History