hcl/zcl/json
Martin Atkins 4bbfa6d6ab json: recovery behavior for the parser
When using the parser to do static analysis and editor integrations, it's
still useful to be able to get the incomplete AST resulting from a parse
error.

Callers that intend to use the returned value to take real actions (as
opposed to just analysis) must check diags.HasError() to determine if
the returned file can be considered valid.
2017-05-20 13:32:12 -07:00
..
ast.go json: recovery behavior for the parser 2017-05-20 13:32:12 -07:00
didyoumean_test.go json: parsing of keywords 2017-05-16 06:51:19 -07:00
didyoumean.go json: Generalize "keywordSuggestion" for general name suggestions 2017-05-20 09:45:15 -07:00
doc.go json: initial scanner implementation 2017-05-15 07:02:13 -07:00
navigation_test.go json: ContextString implementation 2017-05-19 19:33:58 -07:00
navigation.go json: ContextString implementation 2017-05-19 19:33:58 -07:00
parser_test.go json: recovery behavior for the parser 2017-05-20 13:32:12 -07:00
parser.go json: recovery behavior for the parser 2017-05-20 13:32:12 -07:00
peeker.go json: fix buggy peeker.Read 2017-05-16 06:51:19 -07:00
public_test.go json: recovery behavior for the parser 2017-05-20 13:32:12 -07:00
public.go json: recovery behavior for the parser 2017-05-20 13:32:12 -07:00
scanner_test.go json: fix overly-greedy keyword scanning 2017-05-16 07:23:33 -07:00
scanner.go json: recovery behavior for the parser 2017-05-20 13:32:12 -07:00
structure_test.go json: Implement Body.Content 2017-05-20 09:50:48 -07:00
structure.go json: Implement Body.Content 2017-05-20 09:50:48 -07:00
tokentype_string.go json: Generate EOF tokens marking the end of scanning 2017-05-15 07:15:53 -07:00