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

traces don't work well in functions #3484

Closed
Tracked by #3479
pbiggar opened this issue Feb 15, 2022 · 1 comment
Closed
Tracked by #3479

traces don't work well in functions #3484

pbiggar opened this issue Feb 15, 2022 · 1 comment

Comments

@pbiggar
Copy link
Member

pbiggar commented Feb 15, 2022

When you create code in a function for the first time, the function does not have a trace, and the arguments are Incomplete. This means everything is red and when you try to call other functions, nothing works.

Why? The system is built around trace-driven development, but if you don't have a trace, nothing works.

Some possible solutions:

  • Add a warning that you're using the default trace and it doesn't have values for the arguments. Fade the Play button and show a warning about this. Or at least give an error when you try to run something with an incomplete in it.
  • Perhaps default traces should use default values for known types. However, that will result in real values being put in the DB, which the user will then have to dig out.
  • perhaps a dry-run of some sort might be an idea in this situation?
@pbiggar pbiggar mentioned this issue Feb 15, 2022
5 tasks
@StachuDotNet StachuDotNet mentioned this issue Jan 9, 2024
19 tasks
@StachuDotNet
Copy link
Member

merged into #5238

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

2 participants