-
Notifications
You must be signed in to change notification settings - Fork 19
Add funding payments processing #816
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| existing = existing, | ||
| new = new, | ||
| comparison = { obj, newItem -> | ||
| ParsingHelper.compare(obj.effectiveAtMilliSeconds, newItem.effectiveAtMilliSeconds, true) |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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 { |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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...
No description provided.