Part 1)As a trail-chaser, I want to scan a QR code and checkpoint the landmarks I’ve visited on separate trails to track my progress.
Following our discussion during the Scrum Meeting on 01/11/12 (see relevant minutes). This issue has been split into two parts.
This part focuses on implementing the QR scanner in isolation, i.e. it does not effect any current tables within production when activated.
The second part, #54 , deals with integrating this design into active production.
Assessment Criteria
- ~~- [ ] The scanner should scan a QR code and change an internal user-related checkpoint ~~ ( Databse running, not applicable)
-
The code-base should hold a couple of mock-QR codes -
The scanner should be able to successfully scan these mock-QR codes
Tasks
-
Research QR-code scanner API -
Implement any necessary pre-requisites required to get it to function -
Implement the QR code scanner itself -
Implement a couple of mock-QR codes(back-end) -
Attempt to test the scanner using these mock-QR codes ~~[ ] Have the scanning of these mock QR codes change a simple variable from say, a 0 to a 1 [ ] The variables should only be able to be changed once per QR code scanned per session ~~ - Both tasks moved to part 2 after discussion during 05/12/23 scrum meeting ( see applicable minutes) - [ ] Later, replace the simple, above variable with a connection between the scanned QR code and a user's list of landmarks visited as a result of scanning the QR code.
Edited by Rhys Evans