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

brick should have a "fail fast" option #132

Open
aspiers opened this issue May 20, 2020 · 0 comments
Open

brick should have a "fail fast" option #132

aspiers opened this issue May 20, 2020 · 0 comments
Labels
proposal UX Not bugs or features, but areas where the user/developer experience could be better

Comments

@aspiers
Copy link
Contributor

aspiers commented May 20, 2020

When running brick batch files, if a failure happens early on (such as failing to deploy the contract due to a syntax error) then brick continues regardless, typically causing lots more errors which were just side effects of the original error. These subsequent errors do not help - they simply make the root cause harder to find since you have to scroll up to find it. Therefore it would be better if brick stopped running after the first error. Since this is a change in behaviour which might confuse existing users, it could be offered via a new -f option rather than being the new default behaviour.

@aspiers aspiers added proposal UX Not bugs or features, but areas where the user/developer experience could be better labels May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal UX Not bugs or features, but areas where the user/developer experience could be better
Projects
None yet
Development

No branches or pull requests

1 participant