JoshuaPeddle / Visualizing-Technology-Use-by-Age-and-Region

Comp3100. Team 32. Joshua Peddle & Ethan Mc Donald.
0 stars 1 forks source link

Work on translating values + age values fix #31

Closed ethantmc closed 2 years ago

ethantmc commented 2 years ago

This branch has the template for translating values into search queries for us. Please check it over, I have 2 main concerns but have to go to campus and get back before ML: --the code for pushing the returned values to the search terms: I think this removes all (actual) arrays, but if not please raise that/ fix that.

--We're going to push multiple values for the Age, will this work? Will mongoDB and our validation code both accept multiple values for AgeGroup? I can't actually recall any find() case I've seen with multiple values for the same key.

JoshuaPeddle commented 2 years ago

I've pushed a few general fixes/cleanup. Still haven't came up with a good solution for the multiple AgeGroup. Have to run for a few but will be back on it after.

Copied changes from commit:

Deleted the $(".dataset_selector").change(function (e) { function that I had made for debugging.

Changed some properties checks from this.x == to this.prop("x") == As i was reading Jquery docs and read that this is the new standard.

Added if checks for sending the requests from search. Before getResponses and getUsages were being called without checking response_selected and usage_selected

Removed a console.log() causing an undefined.

It seems like incomingValue=verification[2,4] was not working as intended so I changed it to {incomingValue=[verification[2],verification[4]].