Merge Lockup and Flow indexers

[PaulRBerg]

Note

This is a huge task with business/pricing implications. It should not be handled by external contributors.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[PaulRBerg]

We might want to do this in preparation for May 1st @razgraf (to save on Envio subscription costs)

[razgraf]

Maybe we can merge all 3/4 in one 🤔 As a note, we'd have to change the way we query things as well app-side because of the similar entities between indexers (e.g. Stream would turn into FlowStream and LockupStream).

[PaulRBerg]

Maybe we can merge all 3/4 in one

Hopefully, yes!

change the way we query things as well app-side because of the similar entities between indexers

The queries would have to be updated, yes, but I'm hopeful that GraphQL aliases can help us keep the result names the same, i.e. alias streams to FlowStream, etc.