Skip to content
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

shouldRetry property for slots #6

Open
howlowck opened this issue Jul 6, 2018 · 1 comment
Open

shouldRetry property for slots #6

howlowck opened this issue Jul 6, 2018 · 1 comment
Labels
status:potential Feature requested will most likely be accepted but no work planned type:discussion Feature discussion in progress

Comments

@howlowck
Copy link
Collaborator

howlowck commented Jul 6, 2018

Is your feature request related to a problem? Please describe.
Dev should be able to define a function that based on turn count or existing wolf state, whether wolf needs to run the retry function if a response is invalid.

This is helpful if Dev wants the only retry 3 times, and go to another slot.

Describe the solution you'd like

Describe alternatives you've considered
We could the logic in the retryQuery function but it feels dirty.

Additional context

@kevinleung23 kevinleung23 added the rel:slot Pertaining to slot struct and funcitonality label Jul 6, 2018
@kevinleung23 kevinleung23 added the type:discussion Feature discussion in progress label Jul 6, 2018
@kevinleung23 kevinleung23 removed the rel:slot Pertaining to slot struct and funcitonality label Jan 25, 2019
@howlowck
Copy link
Collaborator Author

If a user says a invalid slot and after the validate function, the shouldRetry function should run and determine if it should retry again or simply cancel.

The example we used during discussion is a "number guessing" game where the max number of "retries" is 5.

@howlowck howlowck added the status:potential Feature requested will most likely be accepted but no work planned label Jan 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:potential Feature requested will most likely be accepted but no work planned type:discussion Feature discussion in progress
Projects
None yet
Development

No branches or pull requests

2 participants