You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It works and was super easy to implement but operating on indexes isn't that user-friendly as it should be. I don't want to do much magic but there's an option to extend the interface to be more dynamic.
Using reflection, it's possible to dynamically pass those parameters to the function on the fly so users won't have to play with indexes.
Thanks to this, the context can be simplified to contain only getters for context-based parameters.
ctx.GetInt(userID{})
On the other hand, it put a bit more responsibility to users while changing/writing scenarios. The debugging can be a bit harder, too. IMO it's acceptable but I want to hear feedback from you.
The text was updated successfully, but these errors were encountered:
I'm thinking about changing the step's API a bit. Right now it's very simple.
Parameters from steps are fetched using methods like below:
It works and was super easy to implement but operating on indexes isn't that user-friendly as it should be. I don't want to do much magic but there's an option to extend the interface to be more dynamic.
Using reflection, it's possible to dynamically pass those parameters to the function on the fly so users won't have to play with indexes.
Thanks to this, the context can be simplified to contain only getters for context-based parameters.
On the other hand, it put a bit more responsibility to users while changing/writing scenarios. The debugging can be a bit harder, too. IMO it's acceptable but I want to hear feedback from you.
The text was updated successfully, but these errors were encountered: