@katafrakt @ste @cllns @timriley
Thank you for elaborating! I appreciate that wisdom.
My thought is that if I keep the action layer as thin as possible (just know the right operation(s) to call and what view to display as a result), then I can do both in the same place.
I like the locality of related behavior. I also like that the params
block provides a kind of "type" definition for the operation. This could be used by LSPs to provide annotation and cli/IDE feedback while developing.
=> More informations about this toot | View the thread | More toots from dcrossney@ruby.social
=> View katafrakt@ruby.social profile | View ste@ruby.social profile | View cllns@ruby.social profile | View timriley@ruby.social profile
text/gemini
This content has been proxied by September (3851b).