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 appears that after the initial api request, for subsequent requests the value of the api key param is null. For example, I can successfully pull down a list of tasks ( in this instance I believe the apikey is read directly from the form input value ), but then when I try to immediately edit the time taken for a task, my php debugging indicates that the api key is null.
Refreshing the page fixes the issue, which leads me to believe that although the cookie value for the api key is set, it cannot be read back until a full browser refresh has occured. This may be browser specific behaviour.
Perhaps this could be solved by creating a reference cache to the api key the first time it is read (whether via the input form or cookie) , and only reading from the cookie if the reference is undefined, like a memoization.
The text was updated successfully, but these errors were encountered:
Tested in Chrome on OSX.
It appears that after the initial api request, for subsequent requests the value of the api key param is null. For example, I can successfully pull down a list of tasks ( in this instance I believe the apikey is read directly from the form input value ), but then when I try to immediately edit the time taken for a task, my php debugging indicates that the api key is null.
Refreshing the page fixes the issue, which leads me to believe that although the cookie value for the api key is set, it cannot be read back until a full browser refresh has occured. This may be browser specific behaviour.
Perhaps this could be solved by creating a reference cache to the api key the first time it is read (whether via the input form or cookie) , and only reading from the cookie if the reference is undefined, like a memoization.
The text was updated successfully, but these errors were encountered: