-
Notifications
You must be signed in to change notification settings - Fork 13
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
We should probably only document Operations #443
Comments
@taylordowns2000 I'd appreciate your thoughts on this one! Do we want to be exposing stuff like this from common? And if so, shouldn't it just be an operation which writes to state.data? I sort of see the value of utility functions which you can use inside fn blocks and callbacks - in fact I've started designing adaptors around this pattern (with a But they really complicate the story. Something Aleksa said in Nairobi is that they weren't sure whether something was an Operation and whether/how they could use the return. Maybe we think a bit later about splitting up Operations and Utilities in the docs. |
Hmm - |
I've just been doing some documentation work and I've got a whole bit about how "not all adaptor functions are operations".
And while that's technically true, there's only a small number of exceptions and I don't think any of them are designed for job writers.
Life would be a lot easier if we only publicly documented the actual Operations and hid everything else away.
The text was updated successfully, but these errors were encountered: