Multiple pagakes with various types into one file

[shortcircuit3]

I have a repo with a few packages. I'm trying to generate ts types for the full project but i can't seem to find a way to link the golang types across multiple packages. For example, see the user type reference. The type is in another package, but I want this type to be connected in the tygo generated file.

Any advice?

export interface LoginResponse {
  access_token: string;
  refresh_token: string;
  user?: any /* models.User */;
}
export interface VerifyAccountResponse {
  access_token: string;
  refresh_token: string;
  user?: any /* models.User */;
}

[VeryEvilHumna]

I think you already found a solution, but I still leave mine there for ones who had the same issue.

I had the same issue, ended up solving it with a bash script (a task for a task runner actually) that merges all files in a directory to one big index.d.ts.

But you can include a tag in the filename of emitted ts file for some modules and user.requestGroup.ts, requests.requestGroup.ts, then merge files that had the same tag.

My solution

# generate_types.sh

cd ./backend
tygo generate
cd ../frontend/.tygo_types
cat *.temp.ts > index.d.ts
rm *.temp.ts

# tygo.yaml

packages:
  - path: "example.com/requests"
    output_path: "../frontend/.tygo_types/requests.temp.ts"
  - path: "example.com/user"
    output_path: "../frontend/.tygo_types/user.temp.ts"
  - path: "example.com/auth"
    output_path: "../frontend/.tygo_types/auth.temp.ts"

That's not the most elegant solution, but the simplest one at least. The resulting file looks a bit ugly, because Code generated by tygo. DO NOT EDIT. is repeated for every module, but it works just fine. I hope this helps.

P.S. The feature of merging types from modules in one file seems essential, and it would be great if that would be a built-in feature of tygo.

[jetaggart]

I'm having a similar issue. I have a type that's in a nested package that I don't want to expose to tygo/ts. I have an alias type that that surfaces this type in a package I do allow types to be generated from. For example:

type CreateEntryInput cms.CreateEntryInput

However, this generates an any type. How can I get the full type to come out?

export type CreateEntryInput = any /* cms.CreateEntryInput */;

what I want:

export interface CreateEntryType {
  id: string
}

[ceoshikhar]

I'm having a similar issue. I have a type that's in a nested package that I don't want to expose to tygo/ts. I have an alias type that that surfaces this type in a package I do allow types to be generated from. For example:

type CreateEntryInput cms.CreateEntryInput
However, this generates an any type. How can I get the full type to come out?

export type CreateEntryInput = any /* cms.CreateEntryInput */;
what I want:

export interface CreateEntryType {
id: string
}

Ran into the same issue. The root cause for this in my case is that one package (being parsed) is importing type from another package and tygo isn't going to the referenced package and parsing the referenced type. It just got the name?

I really wanted auto generate types but this issue is just making it unusable for me.