fix(core): format of optional type and getter/setter

[normanzb]

• A naive fix for formatting issue when optional or getter/setter properties used
• All example below was generated with useCodeBlock on

Type with an optional

current the plugin formats optional type in type declaration like so:

code:

export type TypeHasOptional = {
  foo?: string;
};

before the change it generates:

type TypeHasOptional = {
  foo: string;
};

after the change it generates:

type TypeHasOptional = {
  foo?: string;
};

Type with a getter

code:

export type TypeHasGetter = {
  get foo(): string | undefined;
};

before the change it generates:

type TypeHasGetter = {
  get foo
  foo: undefined | string;
};

afterward:

type TypeHasGetter = {
  get foo(): undefined | string;
};

Type with a setter

code:

export type TypeHasSetter = {
  set foo(value: string | undefined);
};

before the change it generates:

type TypeHasSetter = {
  set foo foo: void;
};

afterward:

type TypeHasSetter = {
  set foo(value: undefined | string): void;
};

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
typedoc-plugin-markdown	⬜️ Ignored (Inspect)	Visit Preview		Apr 14, 2025 11:22pm

[tgreyuk]

Thanks - looks good.