Missing operation.go file on processors package

[zkCaleb-dev]

What problem does your feature solve?

The current go-stellar-sdk is missing the operation.go file that was present in the previous package github.com/stellar/go. This file provided access to TransactionOperationWrapper and its associated methods, which are essential for processing transaction operations in my indexer implementation.
Without this functionality, there's no clear migration path for developers who relied on these utilities in the previous SDK version.

What would you like to see?

I would like to see operation.go added back to the SDK, or alternatively, clear documentation on:

1. The replacement/equivalent functionality for TransactionOperationWrapper
2. Migration guide from github.com/stellar/go to the current SDK structure
3. Recommended patterns for handling transaction operation wrapping

Adding operation.go (or its equivalent) would significantly facilitate development and provide continuity for developers migrating from the previous SDK version.

[mollykarcher]

Hello, and thanks for filing! This omission/deletion was actually intentional on our part; all of the contents of the processors package was removed with the exception of the token_transfer processor. The reason for this was entirely because these processors were untested, unmaintained, had not received any updates since prior to Protocol 23, and unfortunately we didn't have the immediate capacity to properly productionalize them. That said, we're hesitant to reintroduce this processor in it's prior form, but we definitely are open to reintroducing equivalent functionality given clear community demand and a well-defined set of use cases we can design and maintain against.

So even the fact that you've raised this is good signal and helps inform our choices here. Along those lines, do you mind expanding a bit on your use-case; exactly which operations you're interested in, what information you're parsing out of them, what kind of product you're building, etc?

In the meantime, this code is always available at this tag and that will continue to be viable until there's a relevant breaking change in the protocol that forces you to upgrade (not the case for the upcoming Protocol 25). At the point that a breaking change is introduced, if there is still no alternative that we've built, I would using that reference to port only the parts of the processor that are relevant to your project.

[zkCaleb-dev]

Hello,

I'm currently building an indexer for the TrustlessWork project, which has its contracts deployed on Stellar, and I've been heavily relying on Stellar's own "wallet-backend" repository. Within that repo, there's an excellent implementation of data indexing, and the version I was basing my work on used an earlier version of the SDK where that package was indeed needed.

That said, it's easily resolved by simply creating that wrapper within my own project, and now everything runs perfectly.

Thank you very much for your response, and I look forward to contributing to Stellar's projects.