d147843c76
- Introduced blog routing using Next.js App Router - Implemented dynamic [slug] pages for blog posts - Added MDX-based content loading via lib/posts - Integrated shared TopBar layout with navigation - Established clear content, lib and component separation
28 lines
1.0 KiB
TypeScript
28 lines
1.0 KiB
TypeScript
import type { RouteMatch } from '../route-matches/route-match';
|
|
import type { RouteDefinition } from '../route-definitions/route-definition';
|
|
import type { Params } from '../request/params';
|
|
type RouteMatchResult = {
|
|
params?: Params;
|
|
};
|
|
export declare class RouteMatcher<D extends RouteDefinition = RouteDefinition> {
|
|
readonly definition: D;
|
|
private readonly dynamic?;
|
|
/**
|
|
* When set, this is an array of all the other matchers that are duplicates of
|
|
* this one. This is used by the managers to warn the users about possible
|
|
* duplicate matches on routes.
|
|
*/
|
|
duplicated?: Array<RouteMatcher>;
|
|
constructor(definition: D);
|
|
/**
|
|
* Identity returns the identity part of the matcher. This is used to compare
|
|
* a unique matcher to another. This is also used when sorting dynamic routes,
|
|
* so it must contain the pathname part.
|
|
*/
|
|
get identity(): string;
|
|
get isDynamic(): boolean;
|
|
match(pathname: string): RouteMatch<D> | null;
|
|
test(pathname: string): RouteMatchResult | null;
|
|
}
|
|
export {};
|