Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚀 Feature: Backend documentation with Swagger #188

Open
2 tasks done
yurimutti opened this issue Dec 11, 2024 · 0 comments
Open
2 tasks done

🚀 Feature: Backend documentation with Swagger #188

yurimutti opened this issue Dec 11, 2024 · 0 comments

Comments

@yurimutti
Copy link
Contributor

🔖 Feature description

We must enhance our API documentation to understand and integrate new partners more easily.

🎤 Why is this feature needed ?

We need to add clarity and coverability to our API.

Example:

What is material array of string?

"materials": [
   "string"
 ],
image

Payload example:

"materials": [
    {
      "materialType": "PLASTIC",
      "weightKg": 5.2
    },
    {
      "materialType": "METAL",
      "weightKg": 3.8
    }
  ],

What materialType we can use ?

export enum ResidueType {
  GLASS = 'GLASS',
  METAL = 'METAL',
  ORGANIC = 'ORGANIC',
  PAPER = 'PAPER',
  PLASTIC = 'PLASTIC',
  TEXTILE = 'TEXTILE',
  LANDFILL_WASTE = 'LANDFILL_WASTE',
}

✌️ How do you aim to achieve this?

Review all DTOs, and schema, improve him, create global entities for users, reports, etc

Add correctly decorators @ApiTags, @ApiOperation, @ApiResponse e @ApiParam

Search and add Swagger best practices and improvements

🔄️ Additional Information

https://staging.api.recy.life/docs#/recycling-reports/RecyclingReportController_createRecyclingReport

👀 Have you spent some time to check if this feature request has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

None

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant