Closed jgkamat closed 7 years ago
Not happening in sprint 2, pushing to sprint 3.
Scanner outputs to keybord, which is good news
Bad news is that the output is any character and can be crazy long, so we're going to have to hash this or use strings as keys.
For simplicity, I'm probably going to just use strings as keys for now, since performance isn't a concern.
This will require us to change the smoker api, so we should do it as soon as possible.
Smoker works fine with the keyboard scanner, hopefully no changes are required with the new one.
If the new scanner uses non-digit keys, we will need to restructure the backend a bit.
this issue will track any progress towards integrating with the new scanner.