Issue 105: Configure and run black and other pre-commit hooks (clean branch) (#1962)

* Configure and run `black` and other pre-commit hooks

Co-authored-by: matt bowen <matthew.r.bowen@omb.eop.gov>

docs/architecture/architecture.mmd

@@ -9,7 +9,7 @@ graph LR
         input --> Voting
         Intake --> Evolution --> Voting
     end
-    
+
     subgraph s["Hosted by Geoplatform.gov"]
         subgraph dp["Data Pipeline (Justice40 Repo)"]
             Voting --> a["Approved Datasets"]
@@ -28,4 +28,4 @@ graph LR
         ScoreCSV --"API (S3 Access)" --> DS["Data Scientists"]
         GeoJSON -- "API (S3 Access)" --> 3["Third Party Apps"]
         MVT -- "API (S3 Access)" --> 3["Third Party Apps"]
-    end
+    end

docs/architecture/geodata-pipeline-arch.mmd

@@ -17,7 +17,7 @@ graph TD
         TS3("TIGER GeoJSON State Files(S3)")-->CombineCensus["Combine Census State Files with Geopandas"]
         CombineCensus-->NCS3("National Census GeoJSON (S3)")
     end
-    
+
     CSV("Full CSV (S3)")-->CGJ
     NCS3-->CGJ
     CGJ["Combine with ogr2ogr + Create GeoJSON (score-geo)"]-->GeoJSON
@@ -31,6 +31,6 @@ graph TD
         Local("Locally stored tiles")--"Option 1"-->TS
         Compressed("Compressed high and low .mbtile files (S3)")--"Option 2"-->TS[/Tileserver-GL/]
     end
-    
+
     TS--"XYZ URL"-->Client
     Uncompressed--"XYZ URL"-->Client["Gatsby+MapLibre"]

docs/decisions/0002-files/AccessibilityComparison.tsv

@@ -9,4 +9,4 @@ OpenStreetMap embed	1		0	The zoom controls' disabled state cannot be programmati
 MapBox GL JS API	1		0	The web map's semantic structure as a distinct piece of content cannot be programmatically determined.	1		0	Control to display attribution and feedback links is not keyboard accessible. [Github PR]	1	1		1	ChromeVox   "Map"   "MapBox logo link" NVDA   "clickable map graphic"   "MapBox logo link"	0	1 tab stop without focus indicator. [Github PR]	0	2/2 targets are too small.	0	1	0	Mapbox logo link opens in a new tab without warning.	0	The "map component" (<canvas tabindex="0">, which acts as a control to both zoom and pan the map display) is missing role. [Github PR]   Control to display attribution and feedback links is missing name and role. [Github PR]	6
 Leaflet JS API	1		0	The web map's semantic structure as a distinct piece of content cannot be programmatically determined. [Github issue]   The zoom controls' disabled state cannot be programmatically determined. [Github issue]	0	Some map labels (i.e. regional/districts) do not meet the minimum contrast ratio (uses OpenStreetMap tiles).	1		1	1		1	ChromeVox   "Zoom in zoom out Leaflet map data copyright OpenStreetMap contributors"   "Zoom in button"   "Zoom out button"   "Leaflet link"   "OpenStreetMap link" NVDA    "clickable Zoom in zoom out Leaflet map data copyright OpenStreetMap contributors zoom in button zoom in zoom out button Zoom out clickable Leaflet link a JS library for interactive maps map data copyright OpenStreetMap link contributors"   "Zoom in button zoom in"   "Zoom out button zoom out"   "clickable Leaflet link a JS library for interactive maps"   "OpenStreetMap link"	0	1 tab stop without focus indicator.   4 tab stops where focus indicators aren't persistently visible. [Github issue]	0	2/2 targets are too small.	0	1	1		0	The "map component" (<div tabindex="0">, which acts as a control to both zoom and pan the map display) is missing name and role. [Github issue]	7
 MapBox Studio embed	1		0	The "Zoom out" control's disabled state cannot be programmatically determined. [Github PR]	1		0	Control to display attribution and feedback links is not keyboard accessible. [Github PR]	1	1		1	ChromeVox   "Map"   "Search edit text"   "Zoom in button"   "Zoom out button"   "Reset bearing to north button"   "MapBox logo link" NVDA   "MapBox Studio frame clickable map graphic"   "Search edit blank"   "Zoom in button zoom in"   "Zoom out button zoom out"   "Reset bearing to north button reset bearing to north"   "MapBox logo link"	0	1 tab stop without focus indicator. [Github PR]	0	7/7 targets are too small.	1	1	0	Mapbox logo link opens in a new tab without warning.	0	The "map component" (<canvas tabindex="0">, which acts as a control to both zoom and pan the map display) is missing role. [Github PR]   Control to display attribution and feedback links is missing name and role. [Github PR]	7
-Bing Maps embed	1		0	Scale bars/rulers are missing contextual information (alternatively should be hidden from ATs).	0	Some map labels (i.e. bodies of water, district labels) do not meet the minimum contrast ratio.	1		1	1		1	ChromeVox   "Bing Maps interact to see more"   "Current level 1 zoom in button"   "Bing Maps link"   "Terms link" NVDA   "Bing Maps frame clickable Bing Maps interact to see more"   "Current level 1 zoom in button zoom in"   "Bing Maps link"   "Terms link terms"	1		0	3/3 targets are too small.	1	1	0	Both the Bing Maps logo and the "Terms" link open in new windows without warning.	0	The "map component" (<div tabindex="0">, which acts as a control to both zoom and pan the map display) is missing role.	8
+Bing Maps embed	1		0	Scale bars/rulers are missing contextual information (alternatively should be hidden from ATs).	0	Some map labels (i.e. bodies of water, district labels) do not meet the minimum contrast ratio.	1		1	1		1	ChromeVox   "Bing Maps interact to see more"   "Current level 1 zoom in button"   "Bing Maps link"   "Terms link" NVDA   "Bing Maps frame clickable Bing Maps interact to see more"   "Current level 1 zoom in button zoom in"   "Bing Maps link"   "Terms link terms"	1		0	3/3 targets are too small.	1	1	0	Both the Bing Maps logo and the "Terms" link open in new windows without warning.	0	The "map component" (<div tabindex="0">, which acts as a control to both zoom and pan the map display) is missing role.	8

docs/decisions/0002-files/Highways.csv

@@ -2,4 +2,4 @@
 Style Loaded,300.22,1195.81,331.85,4460.74,225.97,577.28
 Map Idle,1039.56,1195.63,1184.71,126.85,3837.53,2146.08
 DOM Interactive,126.88,137.59,193.75,131.33,154.01,262.01
-DOM complete,132.70,138.13,193.89,240.13,176.06,353.36
+DOM complete,132.70,138.13,193.89,240.13,176.06,353.36

docs/decisions/0002-files/Maryland.csv

@@ -2,4 +2,4 @@
 Style Loaded,408.89,383.19,439.83,1782.45,147.41,0.00
 Map Idle,207.23,1263.27,1318.54,120.00,1970.86,1659.42
 DOM Interactive,146.15,108.78,171.48,124.38,143.74,269.40
-DOM complete,146.45,109.33,171.69,160.65,166.53,374.69
+DOM complete,146.45,109.33,171.69,160.65,166.53,374.69

docs/decisions/0003-files/adr_process.mmd

@@ -5,8 +5,8 @@ graph TB
     C --> |No| A{Concerns Addressed?}
     A --> |Yes| Merged
     A --> |No| Discussion
-    Discussion --> O{Voting Outcome}    
+    Discussion --> O{Voting Outcome}
     O --> |Accepted| Merged
     O --> |Rejected| Merged
     Merged --> U[Update other Issues]
-    U-->Close
+    U-->Close

docs/decisions/0004-client-side-framework.md

@@ -5,7 +5,7 @@
 - Date: 2021-05-19
 - Tags: front-end, client
 
-Technical Story: https://github.com/usds/justice40-tool/issues/44 
+Technical Story: https://github.com/usds/justice40-tool/issues/44
 
 ## Context and Problem Statement
 
@@ -38,7 +38,7 @@ We need to decide what framework to use for our front end client.
 
 ## Decision Outcome
 
-Chosen option: Gatsby, because it seems to hit the balance between being simple and static-site focused and having capabilities for scaling up features and eventually evolving to a full stack application should we need it. 
+Chosen option: Gatsby, because it seems to hit the balance between being simple and static-site focused and having capabilities for scaling up features and eventually evolving to a full stack application should we need it.
 
 ### Positive Consequences <!-- optional -->
 

docs/decisions/0005-hosting.md

@@ -5,7 +5,7 @@
 - Date: 2021-05-18
 - Tags: Hosting, Server, Geoplatform
 
-Technical Story: https://github.com/usds/justice40-tool/issues/18 + https://github.com/usds/justice40-tool/issues/36 
+Technical Story: https://github.com/usds/justice40-tool/issues/18 + https://github.com/usds/justice40-tool/issues/36
 
 ## Context and Problem Statement
 We need a host for our data pipeline and front end website/app.
@@ -15,7 +15,7 @@ We need a host for our data pipeline and front end website/app.
 - **Speed of launch** - We have a mandate to launch an initial version of our tool by July 27, and we want to get an informational site up much sooner.
 - **Support for continuous integration and delivery** - We need our hosting provider to support a modern software development lifecycle that includes continuous integration and delivery, such as integration with our Github repository and CI/CD tool such as Github Actions.
 - **Ease of implementation** - Ideally we can choose a platform that some of the team has experience with, that doesn't have a steep learning curve, and/or that has good support.
-- **Commitment to open source and process** - Any code used for servers, data processing, or front end hosting must be able to be open source, so there cannot be limitations with regard to where/how code is hosted and shared.  
+- **Commitment to open source and process** - Any code used for servers, data processing, or front end hosting must be able to be open source, so there cannot be limitations with regard to where/how code is hosted and shared.
 
 
 ## Considered Options
@@ -25,7 +25,7 @@ We need a host for our data pipeline and front end website/app.
 
 ## Decision Outcome
 
-We will use Geoplatform.gov for hosting our data pipeline, tile server, and front end client. They have a set of shared service offerings that will enable us to have an open data pipeline from data source to tile API, enabling contributions to data processing at any point as well as enabling data access for users at any point (e.g. whether a user wants to access raw data or GeoJSON or tile format). The diagram below illustrates the proposed system architecture and hosting: 
+We will use Geoplatform.gov for hosting our data pipeline, tile server, and front end client. They have a set of shared service offerings that will enable us to have an open data pipeline from data source to tile API, enabling contributions to data processing at any point as well as enabling data access for users at any point (e.g. whether a user wants to access raw data or GeoJSON or tile format). The diagram below illustrates the proposed system architecture and hosting:
 
 ![diagram](https://raw.githubusercontent.com/usds/justice40-tool/main/docs/architecture/architecture-mmd.svg)
 
@@ -34,11 +34,11 @@ We will use Geoplatform.gov for hosting our data pipeline, tile server, and fron
 - No need to stand up our own servers for data processing or vending tiles
 - No need to find separate static site hosting for our front end
 - Help advance shared geo services for government
-- Code for data transformations can live on an open Github repo and be collaborated on by the community 
+- Code for data transformations can live on an open Github repo and be collaborated on by the community
 
 ### Negative Consequences
 
-- Possible delays or additional work: Some features and offerings we may want to use are still a work in progress on Geoplatform's side, so we may have to help build these out or wait for their release. 
+- Possible delays or additional work: Some features and offerings we may want to use are still a work in progress on Geoplatform's side, so we may have to help build these out or wait for their release.
 
 ## Pros and Cons of Other Options
 
@@ -56,4 +56,3 @@ Cons:
 - Would not have the flexibility to easily run serverless functions if we needed to
 
 ## Links <!-- optional -->
-

docs/decisions/0006-files/adr_diagram.mmd

@@ -8,8 +8,8 @@ graph TB
     C --> |No| A{Concerns Addressed?}
     A --> |Yes| PR
     A --> |No| IP["In Person Discussion"]
-    IP --> O{Voting Outcome}    
+    IP --> O{Voting Outcome}
     O --> |Accepted - add label | PR
     O --> |Rejected - add label | PR
     PR --> PRP["Standard PR Process"]
-    PRP --> Close
+    PRP --> Close

docs/glossary.md

@@ -1,8 +1,8 @@
 # Glossary
 
-This glossary is intended to be a helpful guide to terms and acronyms we use across the Justice40 project and in our open source community. We'll try to keep this list update to date and in alphabetical order for ease of use. If you see an error, please help leave this repo better than you found it by submitting a pull request with the fix :) 
+This glossary is intended to be a helpful guide to terms and acronyms we use across the Justice40 project and in our open source community. We'll try to keep this list update to date and in alphabetical order for ease of use. If you see an error, please help leave this repo better than you found it by submitting a pull request with the fix :)
 
-If you don't see the term you're looking for here, please submit an issue to this repo with the term in question and why you think it should be added. 
+If you don't see the term you're looking for here, please submit an issue to this repo with the term in question and why you think it should be added.
 
 Know a term and its definition that you don't see here? Make a pull request with the term, definition, and reason for inclusion and a team member will review shortly.
 

docs/operations/METHODOLOGY_CHANGE_PROCESS.md

@@ -19,4 +19,4 @@ The methodology for Justice40 will continue to evolve. The steps outlined below
 16. In the frontend, display new indicators in sidepanel
 17. Update copy on methodology page
 18. Update copy on .pdf in download package
-19. Update technical support document (if necessary - TSD will include the final .pdf from download package)
+19. Update technical support document (if necessary - TSD will include the final .pdf from download package)