Skip to content

Conversation

@Jipperism
Copy link
Collaborator

No description provided.

- Introduced a new `log_index` field in the TakerBid schema to track event logs.
- Updated the `parseTakerBidEvent` function to utilize the new `log_index` and simplified claim ID retrieval.
- Refactored currency amount calculation to sum fee amounts directly from the bid parameters.
- Added a migration to the sales table to accommodate the new `log_index` column with a unique constraint on transaction hash and log index.
…les table

- Added a new script to fetch sales with null log indices and update them based on transaction receipts.
- Integrated Supabase client to interact with the sales table and ensure log indices are populated.
- Created a migration to enforce non-null constraints on the log_index column in the sales table.
@github-actions
Copy link

github-actions bot commented Aug 6, 2025

Coverage Report

Status Category Percentage Covered / Total
🟢 Lines 25.89% (🎯 25%) 1577 / 6090
🟢 Statements 25.89% (🎯 25%) 1577 / 6090
🟢 Functions 69.23% (🎯 69%) 36 / 52
🟢 Branches 71.72% (🎯 70%) 104 / 145
File Coverage
File Stmts Branches Functions Lines Uncovered Lines
Changed Files
src/parsing/parseTakerBidEvent.ts 97.68% 92.3% 100% 97.68% 124-127
src/storage/storeTakerBid.ts 43.27% 100% 0% 43.27% 70-166
Generated in workflow #240 for commit 16d5f99 by the Vitest Coverage Report Action

@Jipperism Jipperism force-pushed the bugfix/safe-batch-sale-indexing-hypercert-ids branch from bb00d55 to 6c291c7 Compare August 6, 2025 20:11
@Jipperism Jipperism force-pushed the bugfix/safe-batch-sale-indexing-hypercert-ids branch from a65f8ca to 16d5f99 Compare August 6, 2025 20:28
@Jipperism Jipperism merged commit e279c77 into develop Aug 6, 2025
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant