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

Running a REPL file from the command line doesn't show errors #261

Open
CryptoPascal31 opened this issue Oct 15, 2024 · 0 comments
Open

Comments

@CryptoPascal31
Copy link

Issue description

When starting a REPL file from the command line, Pact 5.0 doesn't show errors. It only shows Load failed

Steps to reproduce

Let's consider the file broken-script.repl. It contains:

; This is a bad function call
(this-function-does-not-exist)

If I load it inside the repl:

$ pact-5
pact>(load "broken-script.repl")
"Loading broken-script.repl..."
broken-script.repl:2:1: Cannot find module:  this-function-does-not-exist
 2 | (this-function-does-not-exist)
   |  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^


pact>

Good ... Pact gives me useful information.

But if I invoke it directly from the command line arguments:

$ pact-5 broken-script.repl
Load failed
$

I have got no information about what's wrong... only Load failed

Expected Behavior

I would expect to have the same level of debug and error reporting when invoking the script from the command line. It's important, since I have some tests suites split in several repl files, batch called by a shell/make script, or GH actions.

From my point of view, it's critical to be able to identify quickly errors when running the test suite.

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