Querying ticks for a climb sometimes fails with "value.getTime is not a function"

[Vichy97]

This is an example response for the climb 673817a585aaf48df33e1fbf

  "errors": [
    {
      "message": "value.getTime is not a function",
      "locations": [
        {
          "line": 6,
          "column": 7
        }
      ],
      "path": [
        "climb",
        "ticks",
        13,
        "dateClimbed"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR"
      }
    }
  ],
  "data": {
    "climb": {
      "ticks": [
        {
          "_id": "673817a585aaf48df33e1fbf",

[wkencel]

I think I resolved this issue

the issue was in the date handling in tick mutations which I verified using graphql on the apollo client

Previously, dates in tick mutations were being stored as null in some cases. This change:

1. Ensures dates are properly converted to timestamps when creating/updating ticks
2. Maintains compatibility with existing tick date formats

The change allows proper date storage and retrieval

Looking at the output, I can see that the dateClimbed is now correctly saved as a timestamp (1469016615000) instead of null!

[wkencel]

Here are my repros of the issue before the change

I need to make sure my change adheres to the typescript enforcement. I'll have a PR up before tomorrow :-)

[Vichy97]

@wkencel thanks for that fix! If you are confident this is resolved, feel free to close the issue

[wkencel]

I don't think I have the permissions to close it. But I've made the change, got the PR approved and merged. May you close it please if you have the permissions to?

[julianlam]

#439