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

[Le #152] Fix case of spec error printing where erroneously passing no arguments causes bad formatting #62

Open
stanislowskij opened this issue Sep 11, 2024 · 0 comments
Assignees
Labels
small bug Something isn't working right, but not fatal

Comments

@stanislowskij
Copy link
Collaborator

⚠️ Imported from legacy repository. This issue is a duplicate of Clojure-Intro-Course/babel-legacy#152.

Small issue, but with babel-spec'd functions in the core library that require multiple arguments, e.g. reduce, take, map, ..., the modified exception output adds an extra space after the function name in the description of the error.

Example:

babel.middleware=> (map)
Wrong number of arguments in (map ): the function map expects one or more arguments but was given no arguments.

This is probably fixable with a simple if block in processor/babel-spec-message, but I am sure this issue is present in different cases where the exception is modified, I just haven't checked yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
small bug Something isn't working right, but not fatal
Projects
None yet
Development

No branches or pull requests

1 participant