NPA-3543: remove trailing space in yaml andassociated editor config

James Taylor · James Taylor · commit bfdad35b375a · 2024-10-29T12:10:53.000Z
diff --git a/.editorconfig b/.editorconfig
@@ -17,9 +17,6 @@ indent_size = 2
 [*.postman_collection.json]
 indent_style = tab
 
-[*.yaml]
-trim_trailing_whitespace = false
-
 [*.js]
 ij_javascript_force_semicolon_style = true
 ij_javascript_use_semicolon_after_statement = false
diff --git a/specification/examples/requests/POST_QuestionnaireResponse/adult-nominates-adult.yaml b/specification/examples/requests/POST_QuestionnaireResponse/adult-nominates-adult.yaml
@@ -1,17 +1,17 @@
 QuestionnaireResponseAdultNominatesAdultRequest:
   summary: Adult nominates Adult access request
   description: |
-    Example proxy access request from an adult (Jill) with NHS number `9000000006` nominating her husband (Tom) with NHS number `9000000005` to act on her behalf. 
-    
+    Example proxy access request from an adult (Jill) with NHS number `9000000006` nominating her husband (Tom) with NHS number `9000000005` to act on her behalf.
+
     Significant things to point out:
 
     - `source.type` should be `Patient` when a patient is nominating a proxy
     - `source.identifier.value` should be the NHS number of the user completing the form - this should correlate with the Identity token in the request
     - `subject.type` should be `Patient` since it is the patient that is the subject of the application
     - `subject.identifier.value` should be the NHS Number of the patient to which the application relates
     - `relatedPerson` demographics are present in the request as a result of being provided by the applicant
-  value: 
-    resourceType: QuestionnaireResponse        
+  value:
+    resourceType: QuestionnaireResponse
     status: "completed"
     authored: "2024-07-15T09:43:03.280Z"
     source:
diff --git a/specification/examples/requests/POST_QuestionnaireResponse/adult-to-adult-with-capacity.yaml b/specification/examples/requests/POST_QuestionnaireResponse/adult-to-adult-with-capacity.yaml
@@ -1,27 +1,27 @@
 QuestionnaireResponseAdultToAdultWithCapacityRequest:
   summary: Adult > Adult (with capacity) access request
   description: |
-    Example proxy access request from an adult (Tom) with NHS number `9000000005` requesting access to act on behalf of his wife (Jill) with NHS number `9000000006`. 
-    
+    Example proxy access request from an adult (Tom) with NHS number `9000000005` requesting access to act on behalf of his wife (Jill) with NHS number `9000000006`.
+
     Significant details to point out:
 
     - `source.type` should be `RelatedPerson` when a proxy is applying
     - `source.identifier.value` should be the NHS number of the user completing the form - this should correlate with the Identity token in the request
     - `subject.type` should be `Patient` since it is the patient that is the subject of the application
     - `subject.identifier.value` should be the NHS Number of the patient to which the application relates
     - `patient` demographics are present in the request as a result of being provided by the applicant
-  value: 
-    resourceType: QuestionnaireResponse        
+  value:
+    resourceType: QuestionnaireResponse
     status: "completed"
     authored: "2024-07-15T09:43:03.280Z"
     source:
       type: "RelatedPerson"
-      identifier:        
+      identifier:
         system: "https://fhir.nhs.uk/Id/nhs-number"
         value: "9000000005"
     subject:
       type: "Patient"
-      identifier:        
+      identifier:
         system: "https://fhir.nhs.uk/Id/nhs-number"
         value: "9000000006"
     questionnaire: "https://api.service.nhs.uk/validated-relationships/FHIR/R4/Questionnaire/01dc6813-3421-4d14-948d-a4888241add1"
diff --git a/specification/examples/requests/POST_QuestionnaireResponse/adult-to-adult-without-capacity.yaml b/specification/examples/requests/POST_QuestionnaireResponse/adult-to-adult-without-capacity.yaml
@@ -1,27 +1,27 @@
 QuestionnaireResponseAdultToAdultWithoutCapacityRequest:
   summary: Adult > Adult (without capacity) access request
   description: |
-    Example proxy access request from an adult (Danny) with NHS number `9876543210` requesting access to act on behalf of an elderly parent (Florence) without capacity wth NHS number `9000000008`. 
-    
+    Example proxy access request from an adult (Danny) with NHS number `9876543210` requesting access to act on behalf of an elderly parent (Florence) without capacity wth NHS number `9000000008`.
+
     Significant details to point out:
 
     - `source.type` should be `RelatedPerson` when a proxy is applying
     - `source.identifier.value` should be the NHS number of the user completing the form - this should correlate with the Identity token in the request
     - `subject.type` should be `Patient` since it is the patient that is the subject of the application
     - `subject.identifier.value` should be the NHS Number of the patient to which the application relates
     - `patient` demographics are present in the request as a result of being provided by the applicant
-  value: 
-    resourceType: QuestionnaireResponse        
+  value:
+    resourceType: QuestionnaireResponse
     status: "completed"
     authored: "2024-07-15T09:43:03.280Z"
     source:
       type: "RelatedPerson"
-      identifier:        
+      identifier:
         system: "https://fhir.nhs.uk/Id/nhs-number"
         value: "9876543210"
     subject:
       type: "Patient"
-      identifier:        
+      identifier:
         system: "https://fhir.nhs.uk/Id/nhs-number"
         value: "9000000008"
     questionnaire: "https://api.service.nhs.uk/validated-relationships/FHIR/R4/Questionnaire/01dc6813-3421-4d14-948d-a4888241add1"
diff --git a/specification/examples/requests/POST_QuestionnaireResponse/mother-child.yaml b/specification/examples/requests/POST_QuestionnaireResponse/mother-child.yaml
@@ -1,17 +1,17 @@
 QuestionnaireResponseMotherChildRequest:
   summary: Mother > Child access request
   description: |
-    Example proxy access request from a mother (Martha) with NHS number `9000000001` requesting access to act on behalf of their child (Timmy) with NHS number `9000000002`. 
-    
+    Example proxy access request from a mother (Martha) with NHS number `9000000001` requesting access to act on behalf of their child (Timmy) with NHS number `9000000002`.
+
     Significant details to point out:
 
     - `source.type` should be `RelatedPerson` when a proxy is applying
     - `source.identifier.value` should be the NHS number of the user completing the form - this should correlate with the Identity token in the request
     - `subject.type` should be `Patient` since it is the patient that is the subject of the application
     - `subject.identifier.value` should be the NHS Number of the patient to which the application relates
     - `patient` demographics are present in the request as a result of being provided by the applicant
-  value: 
-    resourceType: QuestionnaireResponse        
+  value:
+    resourceType: QuestionnaireResponse
     status: "completed"
     authored: "2024-07-15T09:43:03.280Z"
     source:
diff --git a/specification/examples/responses/GET_Consent/adults-consenting.yaml b/specification/examples/responses/GET_Consent/adults-consenting.yaml
@@ -24,7 +24,7 @@ ConsentAdultsConsentingBundle:
             - coding:
                 - system: "https://fhir.hl7.org.uk/CodeSystem/UKCore-AdditionalPersonRelationshipRole"
                   code: Personal
-                  display: "Personal relationship with the patient"                    
+                  display: "Personal relationship with the patient"
         search:
           mode: include
       - fullUrl: "https://api.service.nhs.uk/validated-relationships/FHIR/R4/Patient/DFCC67F5"
@@ -50,7 +50,7 @@ ConsentAdultsConsentingBundle:
           birthDate: "1995-10-22"
           generalPractitioner:
             - type: "Organization"
-              identifier: 
+              identifier:
                 value: "ODS12345"
                 system: "https://fhir.nhs.uk/Id/ods-organization-code"
         search:
diff --git a/specification/examples/responses/GET_Consent/mixed.yaml b/specification/examples/responses/GET_Consent/mixed.yaml
@@ -57,7 +57,7 @@ ConsentMixedBundle:
           birthDate: "2022-10-22"
           generalPractitioner:
             - type: "Organization"
-              identifier: 
+              identifier:
                 value: "ODS12345"
                 system: "https://fhir.nhs.uk/Id/ods-organization-code"
         search:
@@ -111,7 +111,7 @@ ConsentMixedBundle:
             - coding:
                 - system: "https://fhir.hl7.org.uk/CodeSystem/UKCore-AdditionalPersonRelationshipRole"
                   code: Personal
-                  display: "Personal relationship with the patient"                    
+                  display: "Personal relationship with the patient"
         search:
           mode: include
       - fullUrl: "https://api.service.nhs.uk/validated-relationships/FHIR/R4/Patient/DFCC67F5"
@@ -137,7 +137,7 @@ ConsentMixedBundle:
           birthDate: "1995-10-22"
           generalPractitioner:
             - type: "Organization"
-              identifier: 
+              identifier:
                 value: "ODS12345"
                 system: "https://fhir.nhs.uk/Id/ods-organization-code"
         search:
diff --git a/specification/examples/responses/GET_Consent/mother-child.yaml b/specification/examples/responses/GET_Consent/mother-child.yaml
@@ -56,7 +56,7 @@ ConsentMotherChildBundle:
           birthDate: "2022-10-22"
           generalPractitioner:
             - type: "Organization"
-              identifier: 
+              identifier:
                 value: "ODS12345"
                 system: "https://fhir.nhs.uk/Id/ods-organization-code"
         search:
diff --git a/specification/examples/responses/GET_RelatedPerson/errors/invalid-identifier.yaml b/specification/examples/responses/GET_RelatedPerson/errors/invalid-identifier.yaml
@@ -3,10 +3,10 @@ RelatedPersonInvalidIdentifierError:
   description: Error raised due to an invalid RelatedPerson identifier request parameter being specified.
   value:
     resourceType: "OperationOutcome"
-    issue: 
+    issue:
       - severity: error
         code: invalid
-        diagnostics: "Not a valid NHS Number provided for the 'identifier' parameter"            
+        diagnostics: "Not a valid NHS Number provided for the 'identifier' parameter"
         expression: "RelatedPerson.identifier"
         details:
           coding:
diff --git a/specification/examples/responses/GET_RelatedPerson/include-patients.yaml b/specification/examples/responses/GET_RelatedPerson/include-patients.yaml
@@ -2,9 +2,9 @@ RelatedPersonIncludePatients:
   summary: With patient '_include'
   description: |
     Example response containing the details of a single matched candidate proxy relationship between a birth mother and her child.
-    
-    The FHIR Bundle contains a `RelatedPerson` and a `Patient` resource per relationship verified against authoritative sources. 
-    
+
+    The FHIR Bundle contains a `RelatedPerson` and a `Patient` resource per relationship verified against authoritative sources.
+
     `Patient` resources are included in the bundle when the `_include=RelatedPerson:patient` query parameter is specified.
   value:
     resourceType: Bundle
diff --git a/specification/examples/responses/GET_RelatedPerson/without-patients.yaml b/specification/examples/responses/GET_RelatedPerson/without-patients.yaml
@@ -2,9 +2,9 @@ RelatedPersonWithoutPatients:
   summary: Default behaviour
   description: |
     Example response containing the details of two matched candidate proxy relationships between a birth mother and her two children.
-    
-    The FHIR Bundle contains a `RelatedPerson` resource per relationship verified against authoritative sources. 
-    
+
+    The FHIR Bundle contains a `RelatedPerson` resource per relationship verified against authoritative sources.
+
     `Patient` resources are not included by default.
   value:
     resourceType: Bundle
diff --git a/specification/examples/responses/POST_QuestionnaireResponse/success.yaml b/specification/examples/responses/POST_QuestionnaireResponse/success.yaml
@@ -3,10 +3,10 @@ PostQuestionnaireResponseSuccess:
   description: A sample of the payload returned when a QuestionnaireResponse (proxy access request) has been successfully submitted. It contains a unique alpha-numeric reference code to identify the request by.
   value:
     resourceType: "OperationOutcome"
-    issue: 
+    issue:
       - severity: information
         code: informational
         details:
           coding:
             - code: "HDJ2123F"
-              display: "HDJ2123F"    
+              display: "HDJ2123F"
diff --git a/specification/examples/responses/errors/access-denied.yaml b/specification/examples/responses/errors/access-denied.yaml
@@ -3,12 +3,12 @@ AccessDeniedError:
   description: THe request was unsuccessful due to invalid authentication credentials being provided.
   value:
     resourceType: "OperationOutcome"
-    issue: 
+    issue:
       - severity: error
-        code: invalid            
+        code: invalid
         details:
           coding:
             - "system": "https://fhir.nhs.uk/R4/CodeSystem/ValidatedRelationships-ErrorOrWarningCode"
               version: "1"
               code: "ACCESS_DENIED"
-              display: "Missing or invalid OAuth 2.0 bearer token in request."  
+              display: "Missing or invalid OAuth 2.0 bearer token in request."
diff --git a/specification/examples/responses/errors/internal-server-error.yaml b/specification/examples/responses/errors/internal-server-error.yaml
@@ -3,10 +3,10 @@ InternalServerError:
   description: An unexpected condition was encountered preventing the server from fulfilling the request.
   value:
     resourceType: "OperationOutcome"
-    issue: 
+    issue:
       - severity: error
         code: invalid
-        diagnostics: "Internal Server Error - Failed to generate response is present in the response"          
+        diagnostics: "Internal Server Error - Failed to generate response is present in the response"
         details:
           coding:
             - system: "https://fhir.nhs.uk/R4/CodeSystem/ValidatedRelationships-ErrorOrWarningCode"
diff --git a/specification/validated-relationships-service-api.yaml b/specification/validated-relationships-service-api.yaml
