-
Notifications
You must be signed in to change notification settings - Fork 15
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
Alternative syntax suggestions #13
Comments
Hi Kelsey, thanks for the feedback :) I would not compare waterfall is a mini-gem, 200-ish LOC, so it is pretty much flexible. Here is a bonus if you want to get rid of water-ish syntax ;)
Cheers! |
The concept is not unlike
|
@artsyca yes totally. |
No, let's not even go there -- the waterfall metaphor is lovely |
This is an impressive DSL and I really like how it flows. 😉 However, I have to admit I find the concepts of
dam
andoutflows
to be confusing terminology. I love the railway analogy, but as it applies to water I find it a bit confusing. The railway analogy is described assuccess
andfailure
paths so ideally control flow language should invoke those concepts.So when I think of what would be most human readable for handling problems, it would be language like
on_breach
,on_failure
oron_error
.Likewise for assessing state, instead of
outflow
I quite likecontext
which is becoming the idiomatic way we see it done in gems like Interactors.Otherwise I love this DSL! Cheers!
The text was updated successfully, but these errors were encountered: