You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: