feat: yaml options

[urugator]

Types are copied from yaml repo:

export declare function stringify(value: any, replacer?: Replacer | null, options?: string | number | (DocumentOptions & SchemaOptions & ParseOptions & CreateNodeOptions & ToStringOptions)): string;

To keep things simple and in line with getSpecAsJson the signature with options only (without replacer) is not supported.

Fixes: #143

[RobinTail]

I'd suggest to make a reference to the types of the yaml.stringify() parameters instead

[RobinTail]

Suggested change

	// eslint-disable-next-line @typescript-eslint/no-explicit-any
	replacer?: any[] | ((key: any, value: any) => unknown) | null,
	options?:
	| string
	| number
	| (yaml.DocumentOptions &
	yaml.SchemaOptions &
	yaml.ParseOptions &
	yaml.CreateNodeOptions &
	yaml.ToStringOptions)
	replacer?: Parameters<typeof yaml.stringify>[1],
	options?: Parameters<typeof yaml.stringify>[2]

then you'd not need:

• to reproduce internal typing of another module
• to mute ESLint error

That will also make it future resistant (maintainability) if yaml dependency upgrades with changed types, @urugator

[urugator]

I wanted to do that, but it's is not doable for overloaded functions, because TS doesn't know which overload to pick.

[RobinTail]

pick the one having replacer, consider Extract for that, @urugator

[urugator]

Dunno what you mean with the Extract, but turns out Parameters are parameters of the last signature, which is the one we need. So unless they swap or introduce new signatures it should be fine I guess.

[RobinTail]

same advice here
https://github.com/metadevpro/openapi3-ts/pull/144/files#r1730896996

[RobinTail]

I'd say it's too much changes to this file that are unrelated to the proposed feature.

[urugator]

It's done by prettier, should I add Changelog.md to prettier ignore?

[RobinTail]

suggesting to use Parameters<typeof yaml.stringify>
https://www.typescriptlang.org/docs/handbook/utility-types.html#parameterstype

[RobinTail]

nice