MD005 Inconsistent indentation for list items at the same level
This commit is contained in:
@@ -49,32 +49,27 @@ The information to be filled in is divided into three sections:
|
||||
```
|
||||
|
||||
Required fields for the request:
|
||||
|
||||
- **Request method name**: Request method name accepted by the City Census WebService.
|
||||
|
||||
Example:
|
||||

|
||||
|
||||
- **Request Structure**: Structure of the request received by the WebService of the Census of the City Council. The "static" values of this request should be reported. The "dynamic" values related to Document Type, Document Number, Date of Birth and Postal Code should be filled with null value.
|
||||
|
||||
Example:
|
||||

|
||||

|
||||
|
||||
- **Path for document type**: Path in the request structure that sends the Document Type.
|
||||
|
||||
*NOTE: DO NOT FILL IN if the WebService does not require the Document Type to verify a user.*
|
||||
|
||||
Example:
|
||||

|
||||
|
||||
- **Path for document number**: Path in the request structure that sends the Document Number.
|
||||
|
||||
*NOTE: DO NOT FILL IN if the WebService does not require the Document Number to verify a user.*
|
||||
|
||||
Example:
|
||||

|
||||
|
||||
- **Path for date of birth**: Path in the request structure that sends the Date of Birth.
|
||||
|
||||
*NOTE: DO NOT FILL IN if the WebService does not require the Date of Birth to verify a user.*
|
||||
@@ -83,7 +78,6 @@ The information to be filled in is divided into three sections:
|
||||
|
||||
Example:
|
||||

|
||||
|
||||
- **Path for Postal Code**: Path in the request structure that sends the Postal Code.
|
||||
|
||||
*NOTE: DO NOT FILL IN if the WebService does not require the Postal Code to verify a user.*
|
||||
@@ -126,37 +120,30 @@ The information to be filled in is divided into three sections:
|
||||
```
|
||||
|
||||
Required fields to parse the response:
|
||||
|
||||
- **Path for Date of Birth**: In what path of the response is the user's Date of Birth?.
|
||||
|
||||
Example:
|
||||

|
||||
|
||||
- **Path for Postal Code**: In what path of the response is the user's Postal Code?.
|
||||
|
||||
Example:
|
||||

|
||||
|
||||
- **Path for District**: In what path of the response is the user's District?.
|
||||
|
||||
Example:
|
||||

|
||||
|
||||
- **Path for Gender**: In what path of response is the user's Gender?.
|
||||
|
||||
Example:
|
||||

|
||||
|
||||
- **Path for Name**: In what path of the response is the user's Name?.
|
||||
|
||||
Example:
|
||||

|
||||
|
||||
- **Path for the Last Name**: In what path of the response is the user's Last Name?.
|
||||
|
||||
Example:
|
||||

|
||||
|
||||
- **Condition for detecting a valid response**: What response path has to come informed to be considered a valid response and user verified.
|
||||
|
||||
Example:
|
||||
|
||||
Reference in New Issue
Block a user