-
Notifications
You must be signed in to change notification settings - Fork 316
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
Support for metadata #63
Conversation
aman-sai
commented
Dec 15, 2020
- Added a feature such that data can be stored at the fsm level that can be used across the callbacks
- Refer to data.go in examples for demonstration of this feature
I don't think this belongs in the library, at least not in this form. If you could me it optional in some way I might consider it. |
This is a very neat feature. Being able to transition between states , in my use case for example, I need the data the previous state had (maybe the user entered some info that I need in the next state) Instead of adding another dependency eg |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some feedback on implementation and naming.
Sorry for all the comments! 🙂 |
No problem.Glad we had the discussion.Being new to golang ,I learned quite a few things from this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the addition and Merry Christmas!
* added data feature * added commit for NoDataError * added NoDataError * added data.go to demonstrate usage of data feature * renamed data to metadata * removed key level locks from metadata * removed NoDataError Co-authored-by: Aman Sai Ankam <[email protected]>
Cool feature! But i have some worries about similarity of metadata to ctx.Value(), which is build-it package. |
@zhenyanovikov Good observation! That might be useful. Any thoughts @aman-sai and others here? |