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

Better error reporting #65

Open
albertolerda opened this issue Dec 12, 2023 · 0 comments
Open

Better error reporting #65

albertolerda opened this issue Dec 12, 2023 · 0 comments

Comments

@albertolerda
Copy link
Member

Errors are quite difficult to understand, for example in this case the script is

Rule unknown ignore
Given I connect to 'metadata' and do get and output into 'metadata_res'

Given I have a 'float' named 'result' in 'metadata res'
Given I rename 'result' to 'result metadata'
Then print data

and there is no data or keys, the error is a connect is required. In this case, there is one statement and the data is simple so one can track it easily, but it can become problematic with multiple statements.

What about including in the error reporting:

  1. which statement thrown the error
  2. specify the name of the data you are trying to read. For connect, there is just one, but it could be useful in the send.

We could also use the JSON format for error reporting to provide consistency in the output (same format in case of error and success).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant