@ng-doc/app 22.0.0 → 22.2.0

package/types/ng-doc-app-providers-ng-doc-app.d.ts

@@ -22,7 +22,7 @@ interface NgDocApplicationConfig {
      */
     uiKit?: NgDocUiConfig;
     /**
-     * Shiki theme.
+     * Extra Shiki themes and languages for the code that the browser highlights.
      */
     shiki?: NgDocHighlighterConfig;
     /**
@@ -34,6 +34,12 @@ interface NgDocApplicationConfig {
 }
 /**
  * Provides the NgDoc application configuration.
+ *
+ * Add it to the application's providers, or to the `providers` of the route that holds the
+ * documentation, together with the other NgDoc providers: then NgDoc starts only when the reader
+ * opens the documentation, and its code stays out of the application's initial bundle. It starts
+ * with environment initializers, which run where it is provided. The server render waits until
+ * the code highlighter of playgrounds has loaded.
  * @param config - The optional application configuration.
  */
 declare function provideNgDocApp(config?: NgDocApplicationConfig): Array<EnvironmentProviders | Provider>;

package/types/ng-doc-app-providers-texts.d.ts

@@ -0,0 +1,28 @@
+import { Provider } from '@angular/core';
+import { NgDocTextsOverrides } from '@ng-doc/app/interfaces';
+
+/**
+ * Changes the texts NgDoc shows to readers, for example to translate them. Pass the groups and
+ * texts to change; every other text keeps its English default (`NG_DOC_DEFAULT_TEXTS`). NgDoc
+ * ships complete translations in entry points of their own, such as `NG_DOC_TEXTS_DE` from
+ * `@ng-doc/app/texts/de`; pass one first and your changes after it.
+ *
+ * Calls and arguments add up: in one injector they apply in order, so a later one wins for a
+ * text both set, and the providers of a child injector (a lazy route, for example) apply on top of the
+ * texts of its parent. The texts are read when a component is created, so they are fixed per
+ * injector: switch the language by reloading the application, not at run time.
+ * @example
+ * ```typescript
+ * provideNgDocTexts(NG_DOC_TEXTS_DE, { search: { placeholder: 'Handbuch durchsuchen…' } });
+ *
+ * provideNgDocTexts({
+ *   search: { placeholder: 'Dokumentation durchsuchen…' },
+ *   searchPalette: { noResults: ({ query }) => `Keine Ergebnisse für „${query}“` },
+ * });
+ * ```
+ * @param texts - The texts to change, by group, in the order they apply.
+ * @returns The providers to add to the application, a route or a page.
+ */
+declare function provideNgDocTexts(...texts: NgDocTextsOverrides[]): Provider[];
+
+export { provideNgDocTexts };

package/types/ng-doc-app-providers-title.d.ts

@@ -0,0 +1,59 @@
+import { EnvironmentProviders } from '@angular/core';
+import { RouterStateSnapshot } from '@angular/router';
+
+/**
+ * The parts of the current route that `provideNgDocTitle` passes to its function.
+ *
+ * Outside the documentation (a landing page, for example), `categories` is empty and `page`,
+ * `tab` and `api` are not set.
+ */
+interface NgDocTitleContext {
+    /**
+     * The title Angular sets by default: the title of the deepest route that has one. It is not set
+     * when no route of the navigation has a title.
+     */
+    readonly title: string | undefined;
+    /** Titles of the categories that contain the page, the outermost category first. */
+    readonly categories: readonly string[];
+    /**
+     * Title of the guide or the API list. A title in the page's own route replaces it. Not set on
+     * an API page, which sets `api` instead.
+     */
+    readonly page: string | undefined;
+    /**
+     * Title of the active tab, when the page has more than one tab. Not set on a tab titled like
+     * the page, usually its first one.
+     */
+    readonly tab: string | undefined;
+    /** Name of the API declaration, on an API page. */
+    readonly api: string | undefined;
+    /** The router state the title is for. */
+    readonly snapshot: RouterStateSnapshot;
+}
+/**
+ * Builds the browser tab title from the parts of the current route. It runs in an injection
+ * context, so it can call `inject()`. When it returns `undefined`, the title stays as it is.
+ */
+type NgDocTitleFn = (context: NgDocTitleContext) => string | undefined;
+/**
+ * Builds the browser tab title of every navigation with a function that receives the categories,
+ * the page, the tab and the API declaration of the route, so titles like
+ * "Installation · Getting started | NgDoc" need no parsing of route titles.
+ *
+ * Without it, Angular sets the title of the deepest route: the page's (or its tab's) title.
+ * @param titleFn - Builds the title; `undefined` keeps the current title.
+ * @example
+ * ```ts
+ * provideNgDocTitle(({ categories, page, tab, api, title }) => {
+ *   const name = api ?? page;
+ *
+ *   return name
+ *     ? [tab, name, ...[...categories].reverse()].filter(Boolean).join(' · ') + ' | My library'
+ *     : (title ?? 'My library');
+ * });
+ * ```
+ */
+declare function provideNgDocTitle(titleFn: NgDocTitleFn): EnvironmentProviders;
+
+export { provideNgDocTitle };
+export type { NgDocTitleContext, NgDocTitleFn };

package/types/ng-doc-app-providers.d.ts

@@ -3,4 +3,6 @@ export * from '@ng-doc/app/providers/ng-doc-app';
 export * from '@ng-doc/app/providers/page-skeleton';
 export * from '@ng-doc/app/providers/playground-demo';
 export * from '@ng-doc/app/providers/search-engine';
+export * from '@ng-doc/app/providers/texts';
+export * from '@ng-doc/app/providers/title';
 export * from '@ng-doc/app/providers/type-control';

package/types/ng-doc-app-services-content-scroll-intent.d.ts

@@ -14,6 +14,7 @@ interface NgDocInitialContentScrollIntent {
 declare class NgDocContentScrollIntent {
     private readonly browser;
     private readonly router;
+    private readonly location;
     private candidate?;
     private intent?;
     private readonly listeners;
@@ -26,7 +27,10 @@ declare class NgDocContentScrollIntent {
      */
     readonly currentIntent: Signal<NgDocInitialContentScrollIntent | undefined>;
     constructor();
-    /** Starts following router events. Does nothing on the server or when already started. */
+    /**
+     * Starts following router events. Does nothing on the server or when already started. Started
+     * during a navigation, it follows that navigation too.
+     */
     start(): void;
     /**
      * Calls the listener with every change of the intent, and at once with the pending one.
@@ -40,6 +44,12 @@ declare class NgDocContentScrollIntent {
      */
     settle(navigationId: number): void;
     private navigationStarted;
+    /**
+     * Takes the navigation in progress as the candidate. The providers of a lazy route start the
+     * intent while the router loads that route, after the first navigation has started, and its
+     * fragment must still be replayed.
+     */
+    private followCurrentNavigation;
     private navigationEnded;
     private scrolled;
     private publish;

package/types/ng-doc-app-services-highlighter.d.ts

@@ -1,7 +1,7 @@
 import * as _ng_doc_app_tokens from '@ng-doc/app/tokens';
 import * as i0 from '@angular/core';
 import { OnDestroy, Signal } from '@angular/core';
-import { ThemeInput } from 'shiki';
+import { ThemeInput, LanguageInput } from 'shiki/core';
 
 /** Shiki configuration of the code highlighter. */
 interface NgDocHighlighterConfig {
@@ -9,6 +9,13 @@ interface NgDocHighlighterConfig {
      * Themes sources.
      */
     themes?: ThemeInput[];
+    /**
+     * Shiki languages to load besides `angular-html`, the language of playground code, and the
+     * languages it embeds. A language named like one of them replaces it, so register here the
+     * languages of `shiki.langs` in `ng-doc.config.ts` that playground code uses, for example a newer
+     * Angular template grammar.
+     */
+    langs?: LanguageInput[];
     /**
      * Has no effect, and is reported in development mode.
      *
@@ -24,7 +31,9 @@ interface NgDocHighlighterConfig {
     };
 }
 /**
- * Highlights code with Shiki. `provideNgDocApp` initializes it before the application renders.
+ * Highlights code with Shiki. `provideNgDocApp` starts its initialization where it is provided (the
+ * application, or the route that holds the documentation), and the server render waits for it.
+ * Shiki is loaded on demand: `initialize()` imports it.
  */
 declare class NgDocHighlighterService implements OnDestroy {
     private static defaultInitialization?;
@@ -41,12 +50,12 @@ declare class NgDocHighlighterService implements OnDestroy {
     readonly ready: Signal<boolean>;
     /**
      * Loads Shiki with the built-in themes (`github-light`, `ayu-dark` and NgDoc's `css-variables`)
-     * and the given ones. Concurrent and repeated calls share one initialization; a failed one can
-     * be retried.
-     * @param config - Custom Shiki themes to load.
+     * and the given ones, and the given languages. Concurrent and repeated calls share one
+     * initialization; a failed one can be retried.
+     * @param config - Custom Shiki themes and languages to load.
      */
     initialize(config?: NgDocHighlighterConfig): Promise<void>;
-    /** Disposes the highlighter this service created for custom themes. */
+    /** Disposes the highlighter this service created for custom themes or languages. */
     ngOnDestroy(): void;
     private static create;
     /**

package/types/ng-doc-app-services-route-preloader.d.ts

@@ -95,11 +95,23 @@ declare class NgDocRoutePreloader {
     /**
      * Returns the application URL of a link, or `undefined` for a link that leaves the
      * application, opens elsewhere, downloads a file or points into the current page.
+     *
+     * The link is read through the location strategy: with `PathLocationStrategy` the route is the
+     * link's path, and with `HashLocationStrategy` (`withHashLocation()`) it is the link's fragment
+     * (`#/docs/page`), so a fragment that is not a route (`#usage`) is an anchor on the page.
      * @param anchor - The link.
      * @returns The URL relative to the application's base, with its query.
      */
     private linkUrl;
-    /** The base path of the application, ending with a slash. */
+    /**
+     * Whether the location strategy keeps the route in the document's fragment, as
+     * `HashLocationStrategy` does.
+     */
+    private hashLocation;
+    /**
+     * The base path of the application's routes, ending with a slash: the base href, which a
+     * fragment route carries only when `APP_BASE_HREF` sets one.
+     */
     private basePath;
     private destroy;
     static ɵfac: i0.ɵɵFactoryDeclaration<NgDocRoutePreloader, never>;

package/types/ng-doc-app-services-shortcuts.d.ts

@@ -43,6 +43,10 @@ declare const NG_DOC_STORE_SHORTCUTS_KEY: string;
  * the choice is saved in the browser. A site turns them off by default with the shortcuts option
  * of provideNgDocApp. They never run while the reader types in a field or holds Command, Control
  * or Alt. Chords such as Command+K (Control+K) always work.
+ *
+ * Shortcuts run only while the documentation layout is shown: `NgDocRootComponent` turns them on
+ * with `listen()`, so the other pages of an application that shows its documentation under a
+ * route keep their own keys.
  */
 declare class NgDocShortcutsService {
     private readonly document;
@@ -52,6 +56,10 @@ declare class NgDocShortcutsService {
     private readonly appDefault;
     private readonly userChoice;
     private readonly shortcuts;
+    private readonly listener;
+    /** The layouts that listen for the shortcuts; the document listener is on while there are any. */
+    private listeners;
+    private destroyed;
     private themeToggle?;
     /**
      * Whether single-key shortcuts are on: the reader's saved choice, or the site's default.
@@ -59,6 +67,14 @@ declare class NgDocShortcutsService {
      */
     readonly enabled: Signal<boolean>;
     constructor();
+    /**
+     * Runs the shortcuts on key presses until the returned function is called. `NgDocRootComponent`
+     * calls it while the documentation layout is shown; a site with a layout of its own calls it
+     * the same way. Several callers may listen at once: the shortcuts run until each has stopped.
+     * Does nothing on the server.
+     * @returns A function that stops listening; later calls do nothing.
+     */
+    listen(): () => void;
     /**
      * Turns single-key shortcuts on or off for this reader and saves the choice in the browser.
      * @param enabled - Whether single-key shortcuts should run.

package/types/ng-doc-app-texts-ar.d.ts

@@ -0,0 +1,13 @@
+import { NgDocTexts } from '@ng-doc/app/interfaces';
+
+/**
+ * The Arabic texts of NgDoc, for `provideNgDocTexts(NG_DOC_TEXTS_AR)`. Pass your own changes after
+ * them: `provideNgDocTexts(NG_DOC_TEXTS_AR, { search: { placeholder: '…' } })`. NgDoc's layout is
+ * left-to-right, so these texts translate the interface but don't mirror it.
+ *
+ * These translations welcome corrections: open an issue or a pull request at
+ * https://github.com/ng-doc/ng-doc that names the text (its group and key) and your wording.
+ */
+declare const NG_DOC_TEXTS_AR: NgDocTexts;
+
+export { NG_DOC_TEXTS_AR };

package/types/ng-doc-app-texts-de.d.ts

@@ -0,0 +1,12 @@
+import { NgDocTexts } from '@ng-doc/app/interfaces';
+
+/**
+ * The German texts of NgDoc, for `provideNgDocTexts(NG_DOC_TEXTS_DE)`. Pass your own changes after
+ * them: `provideNgDocTexts(NG_DOC_TEXTS_DE, { search: { placeholder: '…' } })`.
+ *
+ * These translations welcome corrections: open an issue or a pull request at
+ * https://github.com/ng-doc/ng-doc that names the text (its group and key) and your wording.
+ */
+declare const NG_DOC_TEXTS_DE: NgDocTexts;
+
+export { NG_DOC_TEXTS_DE };

package/types/ng-doc-app-texts-es.d.ts

@@ -0,0 +1,12 @@
+import { NgDocTexts } from '@ng-doc/app/interfaces';
+
+/**
+ * The Spanish texts of NgDoc, for `provideNgDocTexts(NG_DOC_TEXTS_ES)`. Pass your own changes after
+ * them: `provideNgDocTexts(NG_DOC_TEXTS_ES, { search: { placeholder: '…' } })`.
+ *
+ * These translations welcome corrections: open an issue or a pull request at
+ * https://github.com/ng-doc/ng-doc that names the text (its group and key) and your wording.
+ */
+declare const NG_DOC_TEXTS_ES: NgDocTexts;
+
+export { NG_DOC_TEXTS_ES };

package/types/ng-doc-app-texts-fr.d.ts

@@ -0,0 +1,12 @@
+import { NgDocTexts } from '@ng-doc/app/interfaces';
+
+/**
+ * The French texts of NgDoc, for `provideNgDocTexts(NG_DOC_TEXTS_FR)`. Pass your own changes after
+ * them: `provideNgDocTexts(NG_DOC_TEXTS_FR, { search: { placeholder: '…' } })`.
+ *
+ * These translations welcome corrections: open an issue or a pull request at
+ * https://github.com/ng-doc/ng-doc that names the text (its group and key) and your wording.
+ */
+declare const NG_DOC_TEXTS_FR: NgDocTexts;
+
+export { NG_DOC_TEXTS_FR };

package/types/ng-doc-app-texts-hi.d.ts

@@ -0,0 +1,12 @@
+import { NgDocTexts } from '@ng-doc/app/interfaces';
+
+/**
+ * The Hindi texts of NgDoc, for `provideNgDocTexts(NG_DOC_TEXTS_HI)`. Pass your own changes after
+ * them: `provideNgDocTexts(NG_DOC_TEXTS_HI, { search: { placeholder: '…' } })`.
+ *
+ * These translations welcome corrections: open an issue or a pull request at
+ * https://github.com/ng-doc/ng-doc that names the text (its group and key) and your wording.
+ */
+declare const NG_DOC_TEXTS_HI: NgDocTexts;
+
+export { NG_DOC_TEXTS_HI };

package/types/ng-doc-app-texts-ja.d.ts

@@ -0,0 +1,12 @@
+import { NgDocTexts } from '@ng-doc/app/interfaces';
+
+/**
+ * The Japanese texts of NgDoc, for `provideNgDocTexts(NG_DOC_TEXTS_JA)`. Pass your own changes
+ * after them: `provideNgDocTexts(NG_DOC_TEXTS_JA, { search: { placeholder: '…' } })`.
+ *
+ * These translations welcome corrections: open an issue or a pull request at
+ * https://github.com/ng-doc/ng-doc that names the text (its group and key) and your wording.
+ */
+declare const NG_DOC_TEXTS_JA: NgDocTexts;
+
+export { NG_DOC_TEXTS_JA };

package/types/ng-doc-app-texts-ko.d.ts

@@ -0,0 +1,12 @@
+import { NgDocTexts } from '@ng-doc/app/interfaces';
+
+/**
+ * The Korean texts of NgDoc, for `provideNgDocTexts(NG_DOC_TEXTS_KO)`. Pass your own changes
+ * after them: `provideNgDocTexts(NG_DOC_TEXTS_KO, { search: { placeholder: '…' } })`.
+ *
+ * These translations welcome corrections: open an issue or a pull request at
+ * https://github.com/ng-doc/ng-doc that names the text (its group and key) and your wording.
+ */
+declare const NG_DOC_TEXTS_KO: NgDocTexts;
+
+export { NG_DOC_TEXTS_KO };

package/types/ng-doc-app-texts-pt-br.d.ts

@@ -0,0 +1,12 @@
+import { NgDocTexts } from '@ng-doc/app/interfaces';
+
+/**
+ * The Brazilian Portuguese texts of NgDoc, for `provideNgDocTexts(NG_DOC_TEXTS_PT_BR)`. Pass your
+ * own changes after them: `provideNgDocTexts(NG_DOC_TEXTS_PT_BR, { search: { placeholder: '…' } })`.
+ *
+ * These translations welcome corrections: open an issue or a pull request at
+ * https://github.com/ng-doc/ng-doc that names the text (its group and key) and your wording.
+ */
+declare const NG_DOC_TEXTS_PT_BR: NgDocTexts;
+
+export { NG_DOC_TEXTS_PT_BR };

package/types/ng-doc-app-texts-ru.d.ts

@@ -0,0 +1,12 @@
+import { NgDocTexts } from '@ng-doc/app/interfaces';
+
+/**
+ * The Russian texts of NgDoc, for `provideNgDocTexts(NG_DOC_TEXTS_RU)`. Pass your own changes after
+ * them: `provideNgDocTexts(NG_DOC_TEXTS_RU, { search: { placeholder: '…' } })`.
+ *
+ * These translations welcome corrections: open an issue or a pull request at
+ * https://github.com/ng-doc/ng-doc that names the text (its group and key) and your wording.
+ */
+declare const NG_DOC_TEXTS_RU: NgDocTexts;
+
+export { NG_DOC_TEXTS_RU };

package/types/ng-doc-app-texts-uk.d.ts

@@ -0,0 +1,12 @@
+import { NgDocTexts } from '@ng-doc/app/interfaces';
+
+/**
+ * The Ukrainian texts of NgDoc, for `provideNgDocTexts(NG_DOC_TEXTS_UK)`. Pass your own changes
+ * after them: `provideNgDocTexts(NG_DOC_TEXTS_UK, { search: { placeholder: '…' } })`.
+ *
+ * These translations welcome corrections: open an issue or a pull request at
+ * https://github.com/ng-doc/ng-doc that names the text (its group and key) and your wording.
+ */
+declare const NG_DOC_TEXTS_UK: NgDocTexts;
+
+export { NG_DOC_TEXTS_UK };

package/types/ng-doc-app-texts-zh.d.ts

@@ -0,0 +1,12 @@
+import { NgDocTexts } from '@ng-doc/app/interfaces';
+
+/**
+ * The Simplified Chinese texts of NgDoc, for `provideNgDocTexts(NG_DOC_TEXTS_ZH)`. Pass your own
+ * changes after them: `provideNgDocTexts(NG_DOC_TEXTS_ZH, { search: { placeholder: '…' } })`.
+ *
+ * These translations welcome corrections: open an issue or a pull request at
+ * https://github.com/ng-doc/ng-doc that names the text (its group and key) and your wording.
+ */
+declare const NG_DOC_TEXTS_ZH: NgDocTexts;
+
+export { NG_DOC_TEXTS_ZH };

package/types/ng-doc-app-tokens.d.ts

@@ -1,5 +1,5 @@
 import { InjectionToken, Provider } from '@angular/core';
-import { NgDocContext, NgDocPageProcessor, NgDocPageSkeleton, NgDocTypeControl } from '@ng-doc/app/interfaces';
+import { NgDocContext, NgDocPageProcessor, NgDocPageSkeleton, NgDocTexts, NgDocTextsOverrides, NgDocTypeControl } from '@ng-doc/app/interfaces';
 import { Mermaid } from 'mermaid';
 
 /** Enables one delayed anchor replay after asynchronous NgDoc content is processed. */
@@ -37,7 +37,26 @@ interface NgDocShikiTheme {
 }
 declare const NG_DOC_SHIKI_THEME: InjectionToken<NgDocShikiTheme>;
 
+/**
+ * The English texts of the NgDoc application. They are the texts NgDoc showed before the texts
+ * could be changed, so an application that changes none renders as before.
+ */
+declare const NG_DOC_DEFAULT_TEXTS: NgDocTexts;
+/**
+ * The texts the NgDoc application shows. It resolves to `NG_DOC_DEFAULT_TEXTS` unless
+ * `provideNgDocTexts` changes them. Inject it to show the same texts in your own components.
+ */
+declare const NG_DOC_TEXTS: InjectionToken<NgDocTexts>;
+/**
+ * Applies changes to texts: each group of each change replaces the texts it sets, in order, so a
+ * later change wins. A text set to `undefined` keeps its value. The result is frozen.
+ * @param texts - The texts to change.
+ * @param overrides - The changes, the last one winning.
+ * @returns New texts; `texts` and the changes are left as they are.
+ */
+declare function mergeNgDocTexts(texts: NgDocTexts, ...overrides: readonly NgDocTextsOverrides[]): NgDocTexts;
+
 declare const NG_DOC_TYPE_CONTROL: InjectionToken<NgDocTypeControl>;
 
-export { NG_DOC_CONTENT_ANCHOR_SCROLLING, NG_DOC_CONTENT_SCROLL_POSITION_RESTORATION, NG_DOC_CONTEXT, NG_DOC_MERMAID, NG_DOC_PAGE_CUSTOM_PROCESSOR, NG_DOC_PAGE_PROCESSOR, NG_DOC_PAGE_SKELETON, NG_DOC_ROUTE_PREFIX, NG_DOC_SHIKI_THEME, NG_DOC_TYPE_CONTROL, provideMainPageProcessor, providePageProcessor };
+export { NG_DOC_CONTENT_ANCHOR_SCROLLING, NG_DOC_CONTENT_SCROLL_POSITION_RESTORATION, NG_DOC_CONTEXT, NG_DOC_DEFAULT_TEXTS, NG_DOC_MERMAID, NG_DOC_PAGE_CUSTOM_PROCESSOR, NG_DOC_PAGE_PROCESSOR, NG_DOC_PAGE_SKELETON, NG_DOC_ROUTE_PREFIX, NG_DOC_SHIKI_THEME, NG_DOC_TEXTS, NG_DOC_TYPE_CONTROL, mergeNgDocTexts, provideMainPageProcessor, providePageProcessor };
 export type { NgDocContentScrollPositionRestoration, NgDocShikiTheme };

package/types/ng-doc-app-type-controls-json-control.d.ts

@@ -0,0 +1,38 @@
+import * as _angular_core from '@angular/core';
+import { Signal } from '@angular/core';
+import { NgDocTypeControl, NgDocPlaygroundTexts } from '@ng-doc/app/interfaces';
+import { DIControl } from 'di-controls';
+
+/**
+ * The playground control of array inputs that have no list control, such as `Item[]` or
+ * `[string, number]`: a text area that holds the value as JSON.
+ *
+ * Text that parses sets the value; while the text is not JSON, the field is marked as invalid and
+ * the input keeps its last valid value. An empty field is `undefined`, and the value that the
+ * playground writes is shown as JSON again, so the text and the value always match. It edits any
+ * value that JSON can hold, so it can also be registered for an object type.
+ */
+declare class NgDocJsonControlComponent<T = unknown> extends DIControl<T | undefined> implements NgDocTypeControl<T | undefined> {
+    /** The text of the field. */
+    protected readonly text: _angular_core.WritableSignal<string>;
+    /** Whether the text is not JSON. */
+    protected readonly invalid: _angular_core.WritableSignal<boolean>;
+    /** The rows of the field: its lines, from 2 to 10. */
+    protected readonly rows: Signal<number>;
+    protected readonly texts: NgDocPlaygroundTexts;
+    /** ID of the message that describes invalid text. */
+    protected readonly errorId: string;
+    /** The value that the text stands for. */
+    private textValue;
+    constructor();
+    writeValue(value: T | null | undefined): void;
+    /**
+     * Sets the value from the text of the field, when it is JSON.
+     * @param text - The text of the field.
+     */
+    protected edit(text: string): void;
+    static ɵfac: _angular_core.ɵɵFactoryDeclaration<NgDocJsonControlComponent<any>, never>;
+    static ɵcmp: _angular_core.ɵɵComponentDeclaration<NgDocJsonControlComponent<any>, "ng-doc-json-control", never, {}, {}, never, never, true, never>;
+}
+
+export { NgDocJsonControlComponent };