hi @ianfuin and thanks for giving this a shot :D

this mostly works for me, but I think I've found a small regression:

{
    "anyOf": [
        {
            "title": "host",
            "enum": [
                "example.com",
                "localhost"
            ]
        },
        {
            "title": "ip",
            "enum": [
                "123.123.123.123"
            ]
        }
    ],
    "type": "string",
    "title": "server"
}

would previously turn into

export type Server = Server1 & Server2;
export type Server1 = Host | Ip;
export type Host = "example.com" | "localhost";
export type Ip = "123.123.123.123";
export type Server2 = string;

but is now

export type Server = Server;

all while calling compile with the following options:

compile(
        schema,
        undefined,
        {
            bannerComment: "",
            additionalProperties: false,
            strictIndexSignatures: true,
            sameExplicitTitle: sameExplicitTitle,
        }
    );

The example above is inspired by an anyOf schema with {"format": "ipv4"} and {"format": "hostname"}, which this lib doesn't seem to support - the enum keys are just there to make it at least a tiny bit realistic, but leaving them out gives a similar result.

I can "solve" this by removing either type or title from the outmost object. I can understand removing the title as it's redundant, but the type should just work like that¹

hm, I can also trigger the type Foo = Foo; case using just

import { compile } from 'json-schema-to-typescript/dist/index.js';

console.log(await compile(
    {
        title: "host",
        tsType: "Host"
    },
    undefined,
    {
        bannerComment: ""
    }
));

which yields

export type Host = Host;

BUT that also happens without sameExplicitTitle set. maybe I'm just using tsType wrong, but it still feels related.
possibly also related to #466 (export type StatusBlock = StatusBlock; there)

Closing out stale PRs. Feel free to rebase and re-open if you'd like to revisit this PR.