Creating a new indexer takes you to the indexer

[Ishatt]

Description

The Social VM does not support a callback function to Near.call. So we do not know when the user signed the transaction and submitted it and at what point the indexer will be on-chain ready to be viewed and queried. This ends up in bad UX for the user because we send them to the new indexer(that has not yet been created, so it is buggy).

As an alternative, we will create an Alert that links to the new indexer once the user forks, publishes, or creates a new indexer for added convienence.

[pkudinov]

@roshaans , is there still a blocker on the VM side to implement this?

[roshaans]

@roshaans , is there still a blocker on the VM side to implement this?

No blocker from VM. We simply need to create a QueryAPI indexer that lets clients know through a websocket subscription started upon new indexer creation has been successfully executed on the blockchain, so that client can know when it is safe to redirect the user to the newly created indexer as it does not exist on-chain before instantly.

[gabehamilton]

Could we instead just poll read_indexer_function until it exists?