)]}'
{
  "commit": "10bc22fadfb331a3f397dc9e429d491afe5e2f2b",
  "tree": "700856dcf3c9240b5305b688a70e0423f88f65fc",
  "parents": [
    "ae37bd0e5e370c43e2be40303967eca11bc5e2ad"
  ],
  "author": {
    "name": "martinprobst",
    "email": "martinprobst@google.com",
    "time": "Thu Mar 05 07:20:03 2020 -0800"
  },
  "committer": {
    "name": "Keen Yee Liau",
    "email": "kyliau@google.com",
    "time": "Tue Mar 31 10:27:36 2020 -0700"
  },
  "message": "Turn back on TypeScript error truncation.\n\nTypeScript runs out of memory trying to produce a human readable\ndiagnostic in certain situations (infinitely recursing through anonymous\ntype), see https://github.com/Microsoft/TypeScript/issues/37230.\n\nThat\u0027s a bug, but more generally speaking, the default TypeScript\nbehaviour is to run with error truncation. That\u0027s for a reason: some\nerrors are much more readable with truncation. TypeScript\u0027s core team\nmade the call that error truncation is generally a good idea, so we\nshould follow along unless we have strong data indication otherwise\n(which we don\u0027t).\n\nBeyond that, error truncation being the default means it is the better\ntested path, so we\u0027ll probably save us some trouble in the future by\nkeeping it enabled.\n\nPiperOrigin-RevId: 299096788\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fc1d6f75e23547a6c9d1f54ae165063a8408906c",
      "old_mode": 33188,
      "old_path": "third_party/github.com/bazelbuild/rules_typescript/internal/common/tsconfig.bzl",
      "new_id": "8df9ff4832d0066fbf1aa7d20c9b4b779ef62bea",
      "new_mode": 33188,
      "new_path": "third_party/github.com/bazelbuild/rules_typescript/internal/common/tsconfig.bzl"
    }
  ]
}