Open BellringerQuinn opened 6 days ago
Let's talk about using these wrappers to combine functionality and make them into one call. For example, you don't have to call FeeOptions first, and then send the transaction. We can wrap this into one function per use-case and make it easier to integrate.
Another goal is to let developers call these functions from any blueprint. Right now it seems to be focussed around the Pawn. Ideally, developers can call the auth or setup functions from anywhere, by creating that UObject (or Subsystem later).
Currently, to access the Indexer, write, authenticate, etc. it is all in the same class.
Let's create wrappers that split this functionality out by use case for the integrators.
End goal will eventually be to create subsystems out of this, but let's start with just UObject for now