import { ArticleTopology } from "./Article/Article";
import { ArticleTableTopology } from "./Article/ArticleTable";
import { ArticleTableCellTopology } from "./Article/ArticleTableCell";
import { ArticleTableRowTopology } from "./Article/ArticleTableRow";
import { CardTopology } from "./Card/Card";
import { ChipTopology } from "./Chip";
import { DataGridTopology } from "./DataGrid/DataGrid";
import { DataGridCellListItemTopology } from "./DataGrid/DataGridCellListItem";
import { GridListTopology } from "./GridList";
import { IconTopology } from "./Icon";
import { InfoListTopology } from "./InfoList/InfoList";
import { InfoListCellTopology } from "./InfoList/InfoListCell";
import { InfoListItemTopology } from "./InfoList/InfoListItem";
import { InfoListSectionTopology } from "./InfoList/InfoListSection";
import { DialogTopology } from "./Ontola/Dialog";
import { PaneTopology } from "./Pane/Pane";
import { TableTopology } from "./Table";
/**
 * It's useful to have a central source of valid application topologies. This also provides a
 * location to document the intended usage.
 *
 * A common issue when beginning with link is forgetting to set the correct topology(ies), so
 * defaulting to registering views under all topologies can prevent a lot of headaches. Mind that
 * over-registering might cause the wrong view to be rendered rather than none at all.
 */
export declare const allTopologies: import("@ontologies/core").NamedNode[];
export declare function allTopologiesExcept(...topologies: any[]): import("@ontologies/core").NamedNode[];
export { ArticleTopology, ArticleTableTopology, ArticleTableCellTopology, ArticleTableRowTopology, CardTopology, ChipTopology, DataGridTopology, DataGridCellListItemTopology, DialogTopology, GridListTopology, IconTopology, InfoListTopology, InfoListCellTopology, InfoListItemTopology, InfoListSectionTopology, PaneTopology, TableTopology, };