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
Is your feature request related to a problem? Please describe.
The current routes includes exercise which doesn't make sense. Basically the current for example/exercise/3 route is just a symntathic sugar that hides searchParams like pausePlaces . Describe the solution you'd like
Lets repair that! we should add a new searchParam for handling storing the therapist choice of pointer's pausePlaces. Also it would be nice to add a new route that will store a therapist name/nickname so the final URL will look like:
As you can see now we are more specific in describing the exact place (now it is 2-dimentional (upperRight/UpperLeft... location not just the 1-dimentional like now (left/right). It will be also nice to change the exercise logic to support the brand new pausePlace. It might also require to refactor the Directions enum or at least to create a bew additional one.
Keep in mind that we will have more different exercises so exercise param will be useful the only thing is that instead of placing just a plain number it will be better to name exercise and store it value s as string.
Is your feature request related to a problem? Please describe.
The current routes includes
exercise
which doesn't make sense. Basically the current for example/exercise/3
route is just a symntathic sugar that hidessearchParams
likepausePlaces
.Describe the solution you'd like
Lets repair that! we should add a new
searchParam
for handling storing the therapist choice of pointer'spausePlaces
. Also it would be nice to add a new route that will store a therapist name/nickname so the final URL will look like:As you can see now we are more specific in describing the exact place (now it is
2-dimentional
(upperRight/UpperLeft...
location not just the1-dimentional
like now (left/right)
. It will be also nice to change the exercise logic to support the brand newpausePlace
. It might also require to refactor theDirections
enum or at least to create a bew additional one.Additional context
This might be helpful:
Source of this snippet: https://stackoverflow.com/questions/38797509/passing-array-into-urlsearchparams-while-consuming-http-call-for-get-request
The text was updated successfully, but these errors were encountered: