account for conditions

[bxie]

Design user flow for control conditions

Conditions:

• no system (C1): no recommendations visible
• mixed-initiative (E1): recommendations visible and can choose
• no agency (C2): after each exercise, instructed to go to specific concept and then to certain exercise within in. instructions within any concept (read or write, not both) are always available, but exercises are visible but not clickable unless recommended.

Requirements:

• User will randomly be assigned to a condition on sign up
  • exception: user puts in access code that gets them particular condition
    • code % 47 = {3: c1, 5:e2, 7: c2, else: invalid}
  • assignment based on number of current accounts within certain conditions (e.g. if there are 10 in C1, 9 in E1, 9 in C2, then system will randomly decide to assign either E1 or C2.
• when signing back up, user will get same experience/condition
• backend: associate "condition" property to each new user (for legacy: if null => agency)
  • add property to Users collection

Dev tasks:

• [x] sign-up:
  • [x] UI has optional access code box
  • [x] backend stores condition info
  • [x] condition can be imported from other file
• [x] sign-in
  • [x] app stores user condition in state (& updated firebase rules)
• [x] C1: recommendations do not appear for C1 conditions
• [x] C2: After each exercise, can either go to "next" or "previous". Next is either exercise or unread instruction for recommended exercise. Previous is dropdown pointing back to any visited concept. Worldview is gone (all nav from side nav). ~instructed to go to specific concept and then to certain exercise within in. instructions within that concept (read or write, not both) is available~
  • [x] go to "how code runs," recommend data types exercises at beginning (to account for cold start)
  • [x] don't go to worldview
    • [x] remove left chevron and "back to worldview" buttons in side nav
    • [x] on sign-up/in: go to appropriate concept with sidenav
    • [x] suppress concept map in "/worldview" endpoint for condition C2
  • [x] change side nav
    • [x] exercises not visible unless recommended for condition "C2" only (only visible are completed & recommended)
    • [x] "next" button directs to next exercise or appropriate instruction to learn that exercise
    • [x] prev has dropdown of visited concepts. selecting one will go to side navigation of prev concept
      • [x] trim concept list for only concepts that have recommended exercises
    • [x] progress bars not showing

Changes made (& kept) but not needed for any condition:

• [x] add "back to world view" to side nav (C1, E1)
• [x] worldview signals which concepts have recommendations (not needed for C2, but nice feature anyways)
  • [x] Use exerciseIds from App's state.exerciseRecommendation to highlight identify concepts in worldview which are recommended. (Done w/ itemParams in ModelUpdater.update()). pass state info into world view as props
  • [x] In worldview, on rendering of Cytoscape, set all recommended concepts to have recommended styling (blue border)

[bxie]

Can change style of specific nodes in worldview w/ following line of code let nodeId = "dataTypes"; cy.getElementById(nodeId).style({'border-width': '10px', 'border-color': '#4054B2', 'border-style': 'solid'})

http://js.cytoscape.org/#cy.getElementById http://js.cytoscape.org/#style

[bxie]

fixed #385, so recommendations now persist across refresh, sign-in 👌