You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The parser does its best with any invalid input it gets. We have a few cases where it could be better.
typeA {
field1: Int
|||garbage|||
field2: Int
}
A parse error on line 3 here causes the parser to "unwind" all the way back to the root node before continuing to parse. Here the ideal way to do it would be to eat the garbage and continue parsing the fields definition.
(add more examples as necessary?)
The text was updated successfully, but these errors were encountered:
The parser does its best with any invalid input it gets. We have a few cases where it could be better.
A parse error on line 3 here causes the parser to "unwind" all the way back to the root node before continuing to parse. Here the ideal way to do it would be to eat the garbage and continue parsing the fields definition.
(add more examples as necessary?)
The text was updated successfully, but these errors were encountered: