Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic Vector REPL expressions output warning messages via: vrl::compiler::unused_expression_checker #20840

Closed
hillmandj opened this issue Jul 10, 2024 · 0 comments · Fixed by vectordotdev/vrl#940
Labels
type: bug A code related bug.

Comments

@hillmandj
Copy link

A note for the community

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Problem

After updating to 0.39.0, I noticed an issue with the vector repl, please see the output below:

> VRL REPL commands:
>   help              Learn more about VRL
>   next              Load the next object or create a new one
>   prev              Load the previous object
>   exit              Terminate the program
>
> Any other value is resolved to a VRL expression.
>
> Try it out now by typing `.` and hitting [enter] to see the result.

$ o = { "a" : 1, "b" : 2 }
{ "a": 1, "b": 2 }

$ y = o.a2024-07-10T19:41:47.423618Z  WARN vrl::compiler::unused_expression_checker: unexpected identifier `o` reported as used

2024-07-10T19:41:47.423928Z  WARN vrl::compiler::unused_expression_checker: unexpected identifier `o` reported as used
1

It seems that the expression checker is making it difficult to use the REPL and outputting an error/warn message.

Configuration

No response

Version

0.39.0

Debug Output

No response

Example Data

No response

Additional Context

No response

References

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A code related bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant