)]}'
{
  "commit": "077ca681ace97cf1fb9fc6c925763c0e6c979227",
  "tree": "3abd916f88ad1bfef188a4497da7a150e4163ca3",
  "parents": [
    "c6cbbb88a950ad7e281b8dadbcfb2672b202732f"
  ],
  "author": {
    "name": "philga",
    "email": "philga@1track.com",
    "time": "Fri Oct 18 13:26:15 2019 -0700"
  },
  "committer": {
    "name": "Trevor Ryland",
    "email": "tryland@google.com",
    "time": "Thu Oct 22 17:44:15 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": "b8265a131ed723036873d60935507219087b3dc9",
      "new_mode": 33188,
      "new_path": "EPPlus/FormulaParsing/LexicalAnalysis/SourceCodeTokenizer.cs"
    }
  ]
}