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

Less agrressive errors when rendering functions with a single non-numerical arugment #1199

Closed
berekuk opened this issue Oct 2, 2022 · 0 comments

Comments

@berekuk
Copy link
Collaborator

berekuk commented Oct 2, 2022

Right now the output is too frightening and can convince users that it's their fault, while it's really the playground's limitation.

https://www.squiggle-language.com/playground/#code=eNqrVirOyC8PLs3NTSyqVLIqKSpN1QELuaZkluQXwUQy8zJLMhNzggtLM9PTc1KDS4oy89KVrJTSNCo0FWwVKvQSlWoBJj4auw%3D%3D
Screen Shot 2022-10-03 at 02 51 40

When we get type inference, we'll be able to handle this better. In the meantime, just a grayed out "This function can't be rendered" (with the ability to expand the error on click?..) would be better.

@berekuk berekuk moved this to 🆕 To prioritize in Overview Oct 3, 2022
@berekuk berekuk added this to Overview Oct 3, 2022
@berekuk berekuk closed this as completed in 2d0e643 Oct 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

1 participant