Merge pull request #4578 from satanTime/issues/4577

docs: how to fix Error NG0300 #4577

docs/articles/api/MockBuilder.md

@@ -265,9 +265,9 @@ beforeEach(() => {
 ```
 
 In case of `RouterTestingModule`,
-we need to use [`.keep`](#keep) for both of the modules and [`NG_MOCKS_ROOT_PROVIDERS`](#ngmocksrootproviders-token),
+we need to use [`.keep`](#keep) for both of the modules and [`NG_MOCKS_ROOT_PROVIDERS`](#ng_mocks_root_providers-token),
 and to pass an empty array into `.withRoutes`.
-[`NG_MOCKS_ROOT_PROVIDERS`](#ngmocksrootproviders-token) is needed,
+[`NG_MOCKS_ROOT_PROVIDERS`](#ng_mocks_root_providers-token) is needed,
 because `RouterModule` has many root dependencies which should be also kept. 
 
 ```ts
@@ -296,7 +296,7 @@ beforeEach(() => {
 ## Config
 
 You can customize default behavior of mock things.
-Also, it can be done globally via [`ngMocks.defaultConfig()`](./ngMocks/defaultConfig.md) to avoid repetitions.
+Also, it can be done globally via [`ngMocks.defaultConfig()`](ngMocks/defaultConfig.md) to avoid repetitions.
 
 ### `precise` flag
 
@@ -524,7 +524,7 @@ All other root providers will be replaced with their mocks, even for kept declar
 
 ## Factory function
 
-You might be using other [testing frameworks for angular](../extra/with-3rd-party),
+You might be using other [testing frameworks for angular](/extra/with-3rd-party.md),
 such as [`@ngneat/spectator`](https://www.npmjs.com/package/@ngneat/spectator)
 or [`@testing-library/angular`](https://www.npmjs.com/package/@testing-library/angular).
 

docs/articles/api/MockComponent.md

@@ -34,7 +34,7 @@ The class of a mock component has:
 
 :::tip
 Information about mocking FormControl, ControlValueAccessor, Validator and AsyncValidator
-is in [a different section](../extra/mock-form-controls.md).
+is in [a different section](/extra/mock-form-controls.md).
 :::
 
 ## Simple example
@@ -117,7 +117,7 @@ TestBed.configureTestingModule({
 });
 ```
 
-[`MockBuilder`](./MockBuilder.md) also supports standalone components
+[`MockBuilder`](MockBuilder.md) also supports standalone components
 and allows to mock their imports only for shallow rendering.
 
 ## Advanced example

docs/articles/api/MockDirective.md

@@ -34,7 +34,7 @@ A mock directive has:
 
 :::tip
 Information about mocking FormControl, ControlValueAccessor, Validator and AsyncValidator
-is in [a different section](../extra/mock-form-controls.md).
+is in [a different section](/extra/mock-form-controls.md).
 :::
 
 ## Simple example
@@ -118,7 +118,7 @@ TestBed.configureTestingModule({
 });
 ```
 
-[`MockBuilder`](./MockBuilder.md) recognizes and handles standalone directives.
+[`MockBuilder`](MockBuilder.md) recognizes and handles standalone directives.
 Also, it allows to mock their imports only for shallow testing.
 
 ## Advanced example with attribute directives

docs/articles/api/MockInstance.md

@@ -11,11 +11,11 @@ It is useful, when we want to configure spies before their usage.
 It supports: modules, components, directives, pipes, services and tokens.
 
 The mocks should be created by:
-- [`MockBuilder`](../api/MockBuilder.md)
-- [`MockModule`](../api/MockModule.md)
-- [`MockComponent`](../api/MockComponent.md)
-- [`MockDirective`](../api/MockDirective.md)
-- [`MockProvider`](../api/MockProvider.md)
+- [`MockBuilder`](/api/MockBuilder.md)
+- [`MockModule`](/api/MockModule.md)
+- [`MockComponent`](/api/MockComponent.md)
+- [`MockDirective`](/api/MockDirective.md)
+- [`MockProvider`](/api/MockProvider.md)
 
 ## Define customizations
 
@@ -219,8 +219,8 @@ it('test 3', () => {
 
 It is definitely the right time to use it, if a test fails like:
 
-- [TypeError: Cannot read property 'subscribe' of undefined](../troubleshooting/read-property-of-undefined.md)
-- [TypeError: Cannot read property 'pipe' of undefined](../troubleshooting/read-property-of-undefined.md)
+- [TypeError: Cannot read property 'subscribe' of undefined](/troubleshooting/read-property-of-undefined.md)
+- [TypeError: Cannot read property 'pipe' of undefined](/troubleshooting/read-property-of-undefined.md)
 - or any other issue like reading properties or calling methods of undefined
 
 Or we want to customize a mock declaration which is accessed via:
@@ -244,7 +244,7 @@ class RealComponent implements AfterViewInit {
 
 When we test `RealComponent` we would like to have a mock `ChildComponent`,
 and it would mean, if we replaced it with a mock `ChildComponent` then its `update$` would return `undefined`,
-therefore our test would fail in `ngAfterViewInit` because of [`TypeError: Cannot read property 'subscribe' of undefined`](../troubleshooting/read-property-of-undefined.md).
+therefore our test would fail in `ngAfterViewInit` because of [`TypeError: Cannot read property 'subscribe' of undefined`](/troubleshooting/read-property-of-undefined.md).
 
 In our case, we have a component instance created by Angular, and does not look like `TestBed` provides
 a solution here. That is where `ng-mocks` helps again with the `MockInstance` helper function.

docs/articles/api/MockModule.md

@@ -26,7 +26,7 @@ A mock module provides:
 - respect of tokens with a `useExisting` definition
 - empty objects instead of tokens with a `helperUseFactory` definition
 - base primitives instead of tokens with a `useValue` definition
-- mocks of tokens with a `useValue` definition can read in the section called [How to fix `Type is part of the declarations of 2 modules`](../troubleshooting/declarations-of-2-modules.md).
+- mocks of tokens with a `useValue` definition can read in the section called [How to fix `Type is part of the declarations of 2 modules`](/troubleshooting/declarations-of-2-modules.md).
 
 :::danger
 Do not use `MockModule` on modules which declare the tested declaration. 

docs/articles/api/MockPipe.md

@@ -116,7 +116,7 @@ TestBed.configureTestingModule({
 });
 ```
 
-[`MockBuilder`](./MockBuilder.md) also supports and correctly works with standalone pipes.
+[`MockBuilder`](MockBuilder.md) also supports and correctly works with standalone pipes.
 
 ## Advanced example
 

docs/articles/api/MockProvider.md

@@ -231,7 +231,7 @@ describe('Test', () => {
 :::warning Please note
 The most common error developers meet, when they create mock services, is "**TypeError: Cannot read property 'subscribe' of undefined**".
 
-If we are encountering it too, please read a section called [How to fix TypeError: Cannot read property 'subscribe' of undefined](../troubleshooting/read-property-of-undefined.md).
+If we are encountering it too, please read a section called [How to fix TypeError: Cannot read property 'subscribe' of undefined](/troubleshooting/read-property-of-undefined.md).
 :::
 
 ## Advanced example

docs/articles/api/MockRender.md

@@ -118,7 +118,7 @@ usage of `MockRender` after usage of `TestBed.get`, `TestBed.inject`, `TestBed.c
 triggers an error about dirty `TestBed`.
 
 However, it is still possible to use `MockRender` more than once in a test.
-It requires a reset of `TestBed` (check [`ngMocks.flushTestBed`](./ngMocks/flushTestBed.md)).
+It requires a reset of `TestBed` (check [`ngMocks.flushTestBed`](ngMocks/flushTestBed.md)).
 Please note, that this makes all existing service instances obsolete.
 
 ```ts

docs/articles/api/MockService.md

@@ -9,7 +9,7 @@ If you are here in order to mock **a service** or **a token**,
 please read [corresponding section about MockProvider](MockProvider.md).
 
 If you want to change default mock behavior,
-please read [how to customize mocks](../extra/customize-mocks.md).
+please read [how to customize mocks](/extra/customize-mocks.md).
 :::
 
 If you **need a mock object of a class** which does not belong to Angular declarations, for instance `HTMLInputElement`,

docs/articles/api/ngMocks/change.md

@@ -1,6 +1,6 @@
 ---
 title: ngMocks.change
-description: Documentation about ngMocks.change from ng-mocks library
+description: Documentation about `ngMocks.change` from ng-mocks library
 ---
 
 `ngMocks.change` helps to **simulate external changes of a form control**.
@@ -29,7 +29,7 @@ ngMocks.change(el, 123);
 expect(component.value).toEqual(123);
 ```
 
-or simply with selectors which are supported by [`ngMocks.find`](./find.md).
+or simply with selectors which are supported by [`ngMocks.find`](find.md).
 
 ```ts
 ngMocks.change('input', 123);

docs/articles/api/ngMocks/click.md

@@ -1,6 +1,6 @@
 ---
 title: ngMocks.click
-description: Documentation about ngMocks.click, a simple tool to click any element in unit tests
+description: Documentation about `ngMocks.click`, a simple tool to click any element in unit tests
 ---
 
 There are several ways how to click an element in Angular unit tests.
@@ -27,7 +27,7 @@ ngMocks.click(el.nativeElement, {
 });
 ```
 
-or simply with selectors which are supported by [`ngMocks.find`](./find.md).
+or simply with selectors which are supported by [`ngMocks.find`](find.md).
 
 ```ts
 ngMocks.click('a');
@@ -42,5 +42,5 @@ ngMocks.click(['data-role']);
 ngMocks.click(['data-role', 'link']);
 ```
 
-Under the hood `ngMocks.click` uses [`ngMocks.trigger`](./trigger.md),
-therefore all features of [`ngMocks.trigger`](./trigger.md) can be used.
+Under the hood `ngMocks.click` uses [`ngMocks.trigger`](trigger.md),
+therefore all features of [`ngMocks.trigger`](trigger.md) can be used.

docs/articles/api/ngMocks/crawl.md

@@ -1,6 +1,6 @@
 ---
 title: ngMocks.crawl
-description: Documentation about ngMocks.crawl from ng-mocks library
+description: Documentation about `ngMocks.crawl` from ng-mocks library
 ---
 
 `ngMocks.crawl` is a special function which goes through the passed `DebugNode` or `DebugElement`,
@@ -26,7 +26,7 @@ a different amount of text nodes for the same template.
 ngMocks.crawl(debugElement, callback, textNodes);
 ```
 
-or simply with selectors which are supported by [`ngMocks.find`](./find.md).
+or simply with selectors which are supported by [`ngMocks.find`](find.md).
 
 ```ts
 ngMocks.crawl('div.root', callback, textNodes);

docs/articles/api/ngMocks/defaultConfig.md

@@ -3,7 +3,7 @@ title: ngMocks.defaultConfig
 description: Documentation about ngMocks.defaultConfig from ng-mocks library
 ---
 
-Sets default config for mocks in [`MockBuilder`](../MockBuilder.md#config).
+Sets default config for mocks in [`MockBuilder`](/api/MockBuilder.md#config).
 
 - `ngMocks.defaultConfig( Component, config )` - sets a default config for a component
 - `ngMocks.defaultConfig( Directive, config )` - sets a default config for a directive

docs/articles/api/ngMocks/event.md

@@ -1,6 +1,6 @@
 ---
 title: ngMocks.event
-description: Documentation about ngMocks.event, a simple interface to create custom events in unit tests
+description: Documentation about `ngMocks.event`, a simple interface to create custom events in unit tests
 ---
 
 `ngMocks.event` solves the legacy of IE11, when an event object cannot be created via `new CustomEvent`, but via `document.createEvent`.
@@ -14,4 +14,4 @@ const event = ngMocks.event('click', {
 });
 ```
 
-The created event can be dispatched via [`ngMocks.trigger`](./trigger.md#custom-events).
+The created event can be dispatched via [`ngMocks.trigger`](trigger.md#custom-events).

docs/articles/api/ngMocks/faster.md

@@ -1,6 +1,6 @@
 ---
 title: ngMocks.faster
-description: Documentation about ngMocks.faster from ng-mocks library
+description: Documentation about `ngMocks.faster` from ng-mocks library
 ---
 
 There is a `ngMocks.faster` feature that optimizes setup of similar test modules between tests
@@ -35,7 +35,7 @@ describe('performance:correct', () => {
 If a test creates spies in `beforeEach` then this should be tuned,
 because `ngMocks.faster` will detect this difference and display a notice.
 
-A possible solution is usage of [MockInstance](../MockInstance.md) instead of manual declaration,
+A possible solution is usage of [MockInstance](/api/MockInstance.md) instead of manual declaration,
 or to move creation of spies outside of `beforeEach`.
 
 ## Example of MockInstance
@@ -102,7 +102,7 @@ describe('beforeEach:manual-spy', () => {
 
 ## MockRender
 
-Usage of `ngMocks.faster()` covers [`MockRender`](../MockRender.md) too.
+Usage of `ngMocks.faster()` covers [`MockRender`](/api/MockRender.md) too.
 
 With its help, `MockRender` can be called in either `beforeEach` or `beforeAll`.
 `beforeAll` won't reset its fixture after a test, and the fixture can be used in the next test.

docs/articles/api/ngMocks/find.md

@@ -1,6 +1,6 @@
 ---
 title: ngMocks.find
-description: Documentation about ngMocks.find from ng-mocks library
+description: Documentation about `ngMocks.find` from ng-mocks library
 ---
 
 Returns a found DebugElement which belongs to a component with the correctly typed componentInstance,

docs/articles/api/ngMocks/findInstance.md

@@ -9,7 +9,7 @@ If the element is not specified, then the current fixture is used.
 - `ngMocks.findInstance( fixture?, directive, notFoundValue? )`
 - `ngMocks.findInstance( debugElement?, directive, notFoundValue? )`
 
-or simply with selectors which are supported by [`ngMocks.find`](./find.md).
+or simply with selectors which are supported by [`ngMocks.find`](find.md).
 
 - `ngMocks.findInstance( cssSelector?, directive, notFoundValue? )`
 

docs/articles/api/ngMocks/findInstances.md

@@ -9,7 +9,7 @@ If the element is not specified, then the current fixture is used.
 - `ngMocks.findInstances( fixture?, directive )`
 - `ngMocks.findInstances( debugElement?, directive )`
 
-or simply with selectors which are supported by [`ngMocks.find`](./find.md).
+or simply with selectors which are supported by [`ngMocks.find`](find.md).
 
 - `ngMocks.findInstances( cssSelector?, directive )`
 

docs/articles/api/ngMocks/findTemplateRef.md

@@ -10,7 +10,7 @@ If the element is not specified, then the current fixture is used.
 - `ngMocks.findTemplateRef( debugElement?, id, notFoundValue? )`
 - `ngMocks.findTemplateRef( debugElement?, [attribute, value?], notFoundValue? )`
 
-or simply with selectors which are supported by [`ngMocks.find`](./find.md).
+or simply with selectors which are supported by [`ngMocks.find`](find.md).
 
 - `ngMocks.findTemplateRef( cssSelector?, [attribute, value?], notFoundValue? )`
 

docs/articles/api/ngMocks/findTemplateRefs.md

@@ -10,7 +10,7 @@ If the element is not specified, then the current fixture is used.
 - `ngMocks.findTemplateRefs( debugElement?, id )`
 - `ngMocks.findTemplateRefs( debugElement?, [attribute, value?] )`
 
-or simply with selectors which are supported by [`ngMocks.find`](./find.md).
+or simply with selectors which are supported by [`ngMocks.find`](find.md).
 
 - `ngMocks.findTemplateRefs( cssSelector?, [attribute, value?] )`
 
@@ -40,4 +40,4 @@ const onlyFooters = ngMocks.findTemplateRefs(['myTpl', 'footer']);
 const empty = ngMocks.findTemplateRefs(['myTpl', 'body']);
 ```
 
-More information can be found in [`ngMocks.findTemplateRef`](./findTemplateRef.md).
+More information can be found in [`ngMocks.findTemplateRef`](findTemplateRef.md).

docs/articles/api/ngMocks/formatHtml.md

@@ -51,7 +51,7 @@ becomes
 
 ## ng-container
 
-A cool thing is that `ngMocks.formatHtml` uses [`ngMocks.crawl`](./crawl.md) under the hood
+A cool thing is that `ngMocks.formatHtml` uses [`ngMocks.crawl`](crawl.md) under the hood
 and respects `ng-container`.
 
 so if we have a pointer to `ng-container`, we can assert its content.

docs/articles/api/ngMocks/formatText.md

@@ -41,7 +41,7 @@ header 12
 
 ## ng-container
 
-A cool thing is that `ngMocks.formatText` uses [`ngMocks.crawl`](./crawl.md) under the hood
+A cool thing is that `ngMocks.formatText` uses [`ngMocks.crawl`](crawl.md) under the hood
 and respects `ng-container`.
 
 so if we have a pointer to `ng-container`, we can assert its content.

docs/articles/api/ngMocks/get.md

@@ -1,6 +1,6 @@
 ---
 title: ngMocks.get
-description: Documentation about ngMocks.get from ng-mocks library
+description: Documentation about `ngMocks.get` from ng-mocks library
 ---
 
 Returns a component, directive, service or token, which can be attribute or structural directives,
@@ -25,7 +25,7 @@ const service = ngMocks.get(MyServiceType);
 ```
 
 
-or simply with selectors which are supported by [`ngMocks.find`](./find.md).
+or simply with selectors which are supported by [`ngMocks.find`](find.md).
 
 - `ngMocks.get( cssSelector, Directive, notFoundValue? )`
 ```ts

docs/articles/api/ngMocks/guts.md

@@ -1,6 +1,6 @@
 ---
 title: ngMocks.guts
-description: Documentation about ngMocks.guts from ng-mocks library
+description: Documentation about `ngMocks.guts` from ng-mocks library
 ---
 
 Generates and returns metadata for `TestBed` module.

docs/articles/api/ngMocks/hide.md

@@ -1,9 +1,9 @@
 ---
 title: ngMocks.hide
-description: Documentation about ngMocks.hide from ng-mocks library
+description: Documentation about `ngMocks.hide` from ng-mocks library
 ---
 
-`ngMocks.hide` hides what [`ngMocks.render`](./render.md) has rendered. 
+`ngMocks.hide` hides what [`ngMocks.render`](render.md) has rendered. 
 
 ```ts
 ngMocks.hide(declarationInst);

docs/articles/api/ngMocks/ignoreOnConsole.md

@@ -3,7 +3,7 @@ title: ngMocks.ignoreOnConsole
 description: A way to suppress console logs in Angular unit tests
 ---
 
-`ngMocks.ignoreOnConsole` suppresses `console.log` with a spy (if [auto spy](../../extra/auto-spy.md) is being used).
+`ngMocks.ignoreOnConsole` suppresses `console.log` with a spy (if [auto spy](/extra/auto-spy.md) is being used).
 
 `ngMocks.ignoreOnConsole` suppresses the functions for the current test suite in `beforeAll` and restores in `afterAll`.
 

docs/articles/api/ngMocks/input.md

@@ -1,14 +1,14 @@
 ---
 title: ngMocks.input
-description: Documentation about ngMocks.input from ng-mocks library
+description: Documentation about `ngMocks.input` from ng-mocks library
 ---
 
 Returns value of an `input` of an element.
 It avoids the issue of knowing the name of a component / directive the input belongs to.
 
 - `ngMocks.input( debugElement, input, notFoundValue? )`
 
-or simply with selectors which are supported by [`ngMocks.find`](./find.md).
+or simply with selectors which are supported by [`ngMocks.find`](find.md).
 
 - `ngMocks.input( cssSelector, input, notFoundValue? )`