Skip to content
This repository has been archived by the owner on Mar 12, 2024. It is now read-only.

fix(offchain): fixed timestamp in graphql #231

Merged
merged 1 commit into from
Sep 5, 2023
Merged

Conversation

gligneul
Copy link
Contributor

@gligneul gligneul commented Sep 4, 2023

The timestamp was intepreted in milliseconds, but it should be interpreted in seconds.
Also removes the chrono dependency because it is not necessary.

The timestamp was intepreted in milliseconds, but it should be
interpreted in seconds.
Also removes the chrono dependency because it is not necessary.
@gligneul gligneul requested review from tuler and a team September 4, 2023 22:11
@gligneul gligneul self-assigned this Sep 4, 2023
@gligneul
Copy link
Contributor Author

gligneul commented Sep 4, 2023

Tested with examples and it fixes the issue:

{
  "data": {
    "inputs": {
      "edges": [
        {
          "node": {
            "timestamp": 1693868070
          }
        }
      ]
    }
  }
}

@gligneul gligneul merged commit 0e25296 into release/1.0.x Sep 5, 2023
15 checks passed
@gligneul gligneul deleted the fix/timestamps branch September 5, 2023 12:02
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