Brian Brazil bef9d4e182 Don't include rendered expression in parse errors. (#8177) ... For a sufficiently complex expression, having to render thousands of nodes for every subquery type error can take a while - so don't do that. Signed-off-by: Brian Brazil <brian.brazil@robustperception.io>		2020-11-12 15:25:52 +01:00
..
ast.go	parser.{Expr,Statement} publicly implementable (#7639)	2020-07-25 09:05:58 +01:00
functions.go	Rename package	2020-02-17 16:05:21 +01:00
generated_parser.y	Use ASSIGN when using = inside braces (#7911)	2020-09-09 15:40:02 +05:30
generated_parser.y.go	Move away from testutil, refactor imports (#8087)	2020-10-22 11:00:08 +02:00
lex.go	Use ASSIGN when using = inside braces (#7911)	2020-09-09 15:40:02 +05:30
lex_test.go	Testify: move to require (#8122)	2020-10-29 09:43:23 +00:00
parse.go	Don't include rendered expression in parse errors. (#8177)	2020-11-12 15:25:52 +01:00
parse_test.go	Don't include rendered expression in parse errors. (#8177)	2020-11-12 15:25:52 +01:00
printer.go	Move away from testutil, refactor imports (#8087)	2020-10-22 11:00:08 +02:00
printer_test.go	Testify: move to require (#8122)	2020-10-29 09:43:23 +00:00
value.go	promql: use explicit type declare instead of string. (#7716)	2020-08-02 09:57:38 +01:00