Fixed neighborhood name commas breaking csv formatting #3392
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #3390
Neighborhood names containing commas would break the CSV file formatting, acting as an unintended delimiter. This PR adds double quotes around each instance of neighborhood names being referenced in CSV files, namely in these API calls:
Before/After screenshots (if applicable)
Before:
After:
Testing instructions
localhost:9000/v2/access/attributes?lat1=<x1>&lng1=<y1>&lat2=<x2>&lng2=<y2>&filetype=csv
localhost:9000/v2/access/attributesWithLabels?lat1=<x1>&lng1=<y1>&lat2=<x2>&lng2=<y2>&filetype=csv
localhost:9000/v2/access/score/neighborhoods?lat1=<x1>&lng1=<y1>&lat2=<x2>&lng2=<y2>&filetype=csv
a. If you have coordinates with a known neighborhood with commas in the name, use that instead! (i.e. https://sidewalk-chicago.cs.washington.edu/v2/access/attributes?lat1=41.863085&lng1=-87.661878&lat2=41.874468&lng2=-87.646729&filetype=csv on the Chicago database)
Things to check before submitting the PR