/users/{userId}/tasks Pagination

[unicornsleuth]

Closes #259

Format of query string now accepted: /users/{userId}/tasks?count={count}&page={page}

note: failing to pass in the count or page values will return 1st 10

Other Changes: fix caching in /users

To Test:

• (1) in VSCode add the line "CACHE_TOGGLE": "On" to functions/local.settings.json

  • make sure this file also contains the variables ENV_DATABASE_CONNECTION_STRING, ENV_REDIS_KEY, ENV_REDIS_HOST, and ENV_REDIS_PORT (all available in key vault)

• (2) under the "Run/Debug" tab in VSCode, run the functions

• (3) go to Postman, c/p the endpoint for /users that VSCode will display on the terminal & enter integer values for {count} and {page}

• (4) run a GET

  • you should see over {count} results in Postman
  • VSCode terminal should display the following:
  • 
  • (if not, skip to step 6)

• (5) run another GET

  • VSCode terminal should display the following:
  • 

• (6) run a POST with a body like so:

  {
  "firstName": "First",
   "lastName": "Last",
  "email": "email@email.com"
  }

  • VSCode terminal should display the following:
  • 

• (7) run (yet) another GET

  • VSCode terminal should display message from (4) again

• (8) Change the CACHE_TOGGLE value in /functions/local.settings.json to "Off"

• (9) run a GET

  • VSCode terminal should display the following:
  • 

• (10) run a POST with a body like in (6)

  • VSCode terminal should display the following:
  • 
  • (11) run a last GET
  • VSCode terminal should display the same as in (9)

[kieranmiguel]

Great stuff. I noticed the cache_toggle is currently set to on/off in your code. Personally I don't know how to access the key vault, but I know it was initially set as true/false so could cause issues after deployment. Since you did all the work I am going to try to set up redis queries so we don't need to expire caches in a time limit, and can instead expire based on taskid. I'll message if I get that working.