Repository navigation
feat: expose cached on-chain subscription status - #1099
Conversation
|
@TekenujUi90 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
422f597 to
1407c5f
Compare
|
@Chucks1093 I rebased this branch on current main and resolved the indexer conflict while preserving both the upstream invoice/TWAP/depth/whitelist/governance handlers and this PR’s subscription-created handler. Please review and merge when the checks pass. |
|
Conflict |
# Conflicts: # src/modules/indexer/indexer-pipeline.service.ts
|
36e2c91 to
e3d1412
Compare
Re-add the SubscriptionCreated handler on top of the upstream indexer pipeline instead of replacing the file, so the newer poll, curve-update, milestone, co-creator, reserve and tip handlers from main are kept.
✅ PR Ready for ReviewDue to a recent malware incident affecting our repositories, all PRs are required to pass automated security checks before being reviewed for merging. This PR has passed all automated checks:
Next step: Please share this PR link in our Telegram group so a maintainer can review and merge it: https://t.me/c/accesslayerorg/8514 |
|
@Chucks1093 This PR is open, conflict-free, and its required checks are passing. Could you please review and merge it when ready? Thanks. |
@accesslayerorg I updated this branch from main and resolved the merge conflicts. Please review and merge when ready.
Fixes #1079