Skip to content

Conversation

@ruixhuang
Copy link
Contributor

No description provided.

@ruixhuang ruixhuang marked this pull request as ready for review June 17, 2025 17:30
existing = existing,
new = new,
comparison = { obj, newItem ->
ParsingHelper.compare(obj.effectiveAtMilliSeconds, newItem.effectiveAtMilliSeconds, true)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think effectiveAtMilliSeconds exist in the Indexer response. Are you creating this key later in the pipeline?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the output data structure (actually copied from v3 two years ago). The data of this field comes from the "createdAt" field of the indexer response:

effectiveAtMilliSeconds = createdAt.toEpochMilliseconds().toDouble()

existing = existing,
incoming = new,
timeField = { item ->
item?.effectiveAtMilliSeconds?.toLong()?.let {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same question here. Also I think if you keep this key

effectiveAtMilliSeconds -> effectiveAtMilliseconds

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

effectiveAtMilliSeconds is part of the output structure, so it should be fine...

jaredvu
jaredvu previously approved these changes Jun 18, 2025
@ruixhuang ruixhuang merged commit 07bafc4 into main Jun 18, 2025
3 checks passed
@ruixhuang ruixhuang deleted the feature/fundingPayments branch June 18, 2025 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants