Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If the type signature isn't enough to fully constrain that, you need to fix your typing.

If you have a `Foo` object, it should always be able to do every possible thing a `Foo` can do.

If you need to do something first, it should be a required argument to whatever lets you construct a `Foo` in the first place.



Please constrain function signatures of these: https://developer.auth0.com/resources/labs/actions/sync-stri... and https://github.com/stripe-samples


I see nothing there that seems fundamentally problematic, but I'm not writing type definitions for someone's entire commercial API.

Callbacks are always Hell of course.


Please tell me how you deduce proper payment and auth flows from a function signature alone.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: