Issues Template

## Express Route template

**labels**: `backend`, `route`

**Title**: METHOD/full-route , `eg:` `POST/login`

**Description**
What route should do

**Protected**: Yes/No

**Required middlewares**: if exist
---
**Response**:
maybe success or error:
Error :
```js
{
status:400,
message:'Bad reqeust'
}
```
Success
```js
{
status:200,
data: [...please fill sample of data] ,
}
```
---
**Request body**:
```
{
x: "Y"
}
```
**Validation**
```
{
x: string
}
```
---

**Tests**: test all potential cases for the route itself.

The issue describes an Express route issue template but does not name a repository file or configuration entry point. First inspect the repository's existing issue-template setup and compare its conventions with the fields shown here; done means the template captures route details, responses, request validation, middleware, protection, and tests.

Written by the indexing model from the issue text.