Skip to content
This repository was archived by the owner on Jun 8, 2020. It is now read-only.

Conversation

@dp770
Copy link

@dp770 dp770 commented Mar 23, 2020

Timestamp attribute is added to HitbtcOrderBookWithTimestamp (extension of HitbtcOrderBook)

@@ -0,0 +1,40 @@
package info.bitrich.xchangestream.hitbtc.dto;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Copy link
Author

Choose a reason for hiding this comment

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

Locally, I extended HitbtcAdapters.adaptOrderBook method from the org.knowm.xchange library to support timestamps. However, ideally, it should be updated at the source library, rather than "overridden" here. Having said that, I'm fine to commit it as well if it does make sense.

@badgerwithagun
Copy link
Collaborator

Thanksfor your contribution @dp770! Just a couple of thoughts/questions.

dp770 and others added 6 commits May 3, 2020 20:10
…stamp. Using built-in date time formatter with UTC timezone.
…stamp. Using built-in date time formatter with UTC timezone.
…stamp. Using built-in date time formatter with UTC timezone.
…rt_in_orderbook' into HitBTC_timestamp_attribute_support_in_orderbook
@badgerwithagun
Copy link
Collaborator

This project is in the process of being merged into the XChange project and no further PRs will be merged here. Once the projects have been merged, there may be a short stabilization period where there will be large-scale renaming of classes and packages, which may cause conflicts. You are advised to wait at least a week from now and then resubmit your PR on the XChange project. Thank you for your support!

@badgerwithagun
Copy link
Collaborator

You can now resubmit your PR on XChange. This project will shortly be marked as archived.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants