Krešimir Klas
Krešimir Klas
> What implications (if any) does adding prefixes to type definition names like `idl::Bar` and `extern_program::some_module::Foo` have on type inference during IDL parsing in the TS package? I touched upon...
> so the introduction of the path segmented naming via full_path was added for name conflicted resolution (correct me if I'm wrong). Exactly. Name conflicts don't happen super often but...
You might want to check out [anchor-client-gen](https://github.com/kklas/anchor-client-gen) - it has tuple enum support.
@y2kappa I argue that: 1) if you have the same contract that is forked and deployed on another address, they should be treated as two different programs and codegen them...
Closed with #62
I will take a look into this again when I finish what I'm currently working on and try to push it through. I think there might be a cleaner solution...
Yes, I also think this is the right approach. My only concern with it previously was the generics support, but now with this implemented it should be very solid. It...
@acheroncrypto > How should the external wrapper types like TokenAccount work? Currently it doesn't seem to build the IDL with an SPL account. Should we skip the known types? Do...
> The former, IDL build fails because those types don't have __anchor_private_gen_idl_type method. As you know, they implement AnchorSerialize trait but the trait itself doesn't have the IDL print functionality,...
@AnderUstarroz yes, it will fix it