[dynamic-parsers] Use additional programs when parsing data

[unek]

parseInstruction refuses to recognize createAssociatedTokenIdempotent which is an instruction of the ATA program included as a part of the token program IDL, and instead attempts to parse it as initializeAccount, despite programAddress, discriminator and account count mismatch.

[lorisleiva]

Since the parse function is only suppose to work within the context of a program, I would say this is the expected behaviour.

You should however have generated functions for the Associated Token program amongst the JS clients of both token programs.

[unek]

parseInstruction takes a root node so should it really work within the context of one program? i do have both spl-token and token-2022 programs shipped with two slightly different ata programs as additionalPrograms and that's also causing me plenty of conflicts and headaches.

[lorisleiva]

Oh I see sorry you mean parseInstruction from the dynamic-parsers package? Interesting, yeah we probably should look into additional programs as well since the information is there.

[unek]

yeah, causes a headache with the associated token program IDLs which are embedded in both spl-token and token-2022 IDLs, but somehow incompatible.

[joefitter]

+1 for this feature!

[lorisleiva]

I'll tackle this in the future as right now I am focusing my effort on Solana Kit v3 but if anyone want to submit a PR before then, I'm happy to help in the reviewing process. 🙏