)]}'
{
  "commit": "76196e4d03e56abb660a651b73c31eaa8ac99324",
  "tree": "e536c4f3b9910628e3a69f8e8acee6fb8d509a3d",
  "parents": [
    "00ddba5b0030f8e7a61667ccf673ddd08f20858f"
  ],
  "author": {
    "name": "philga",
    "email": "philga@1track.com",
    "time": "Thu Oct 17 11:55:29 2019 -0700"
  },
  "committer": {
    "name": "Trevor Ryland",
    "email": "tryland@google.com",
    "time": "Thu Oct 22 17:43:57 2020 -0600"
  },
  "message": "Fix parser invalid index error that occurred when a field name was the same as an Excel function name. EPPlus treated the field name as a \u0027Function\u0027 even if the name was not followed by a left paranthesis to enclose the function arguments following the \u0027Function\u0027 name. We now treat the field name as a \u0027Name\u0027 rather than as a \u0027Function\u0027 when no left parathensis follows the field name. This is true even if the field name is the same as an Excel function name.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a0d5d47f076c53f2c7a3c5d3acc555463c027ca5",
      "old_mode": 33188,
      "old_path": "EPPlus/FormulaParsing/LexicalAnalysis/SourceCodeTokenizer.cs",
      "new_id": "f397e84d4e138d06913fcccb42299a12496677d4",
      "new_mode": 33188,
      "new_path": "EPPlus/FormulaParsing/LexicalAnalysis/SourceCodeTokenizer.cs"
    }
  ]
}