The quizzes are the same at this time and are pulling from a quizData.json file using a react quiz component library.
The Step to Guidance step by step is using WeiGuang's custom back/next code, but in the upcoming sprint I'd like to replace it with a robust component library see #180 (I attempted to use react-albus but it requires some restructuring of pieces - will discuss).
Types of changes
What types of changes does your code introduce to the app?
Put an x in the boxes that apply
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist
[x] Code compiles correctly
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[x] All tests passing
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules
Further comments
Worked on the weekend to push the app forward a couple of days - spoke to Jen about this. The work is a bit messy, but I tried to push forward as much of components and styling as possible.
Proposed changes
Rapid prototyping for the v3 iteration of the application: https://sketch.cloud/s/jPQEW
Includes roughly put together:
quizData.jsonfile using a react quiz component library.react-albusbut it requires some restructuring of pieces - will discuss).Types of changes
What types of changes does your code introduce to the app? Put an
xin the boxes that applyChecklist
Further comments
Worked on the weekend to push the app forward a couple of days - spoke to Jen about this. The work is a bit messy, but I tried to push forward as much of components and styling as possible.