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

improve "build on run" UX for source commands #69

Closed
progrium opened this issue Jan 23, 2024 · 2 comments
Closed

improve "build on run" UX for source commands #69

progrium opened this issue Jan 23, 2024 · 2 comments
Assignees
Labels
good first issue Good for newcomers
Milestone

Comments

@progrium
Copy link
Contributor

We support "build on run" for commands implemented as Go source directories, but we get the output of the build compiler when its run. The build compiler should probably only output when there is a problem and leave the progress output behind a verbose flag. This would make "build on run" a more seamless experience.

@Parzival-3141
Copy link
Collaborator

As of 214113a this is "technically" complete, though only because all build output gets ignored in proc.go. AFAICT this is blocked by #64 since we don't have a good way of using stdio from within the kernel. In the meantime we could workaround this by piping build's stdout/err to the browser console.

@taramk taramk mentioned this issue Feb 14, 2024
@progrium
Copy link
Contributor Author

I recently set the default stdio for the kernel to be logged with console.log so this is good for now.

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

No branches or pull requests

2 participants