Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

The callback gets incorrect info about the previous prediction #20

Closed
dnesteryuk opened this issue Feb 16, 2017 · 1 comment
Closed
Labels
Milestone

Comments

@dnesteryuk
Copy link
Collaborator

It happens when the previous prediction is undefined because the engine didn't make a prediction.

@dnesteryuk dnesteryuk added the bug label Feb 16, 2017
@dnesteryuk dnesteryuk added this to the 0.0.1 milestone Feb 16, 2017
dnesteryuk added a commit that referenced this issue Feb 18, 2017
…#20)

The second argument passed to the user's callback must be undefined when:

- it is a first visit of the user;
- the page gets refreshed;
- the engine hasn't made a prediction for the previous page

Implementing these, the user can track more real accuracy.
@dnesteryuk
Copy link
Collaborator Author

It is already fixed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant