#I find it weird / frustrating that

1 messages · Page 1 of 1 (latest)

wild wraith
#

This has been the subject of pretty exhaustive debate already - I think both options just suck. [Some] users don't want to commit 3k lines of code, and we don't want 3k lines of committed code in a 3 year old module to break because its generated code is out of date

So it's up to the user to decide which trade-offs they want (rm .gitignore), and we always codegen to cover the second part.

slate patrol
#

Yes, I remember that initially we required a dagger develop on any changes to signatures, and first testers just forgot or found it too cumbersome to do it every time. It added a lot of friction. That's when we started doing that generation automatically on function execution as well.

barren lagoon
#

Cc @merry haven 👆since you noticed me occasionally doing a dagger develop unnecessarily after making a change.