Response from `/search` and `/projects` have different naming conventions

modrinth / labrinth

Our Rust-based backend utilizing the actix-web framework to serve Modrinth's API.

https://modrinth.com

GNU Affero General Public License v3.0

509 stars 73 forks source link

Response from `/search` and `/projects` have different naming conventions #908

Open AlexanderHott opened 2 months ago

AlexanderHott commented 2 months ago

Describe the bug

The response from /search includes an array of projects with a "project_id": "AABBCCDD" attribute while the /projects response has an array of projects with an "id": "AABBCCDD" attribute.

Steps to reproduce

Look at the api spec

Expected behavior

The naming convention should match. Since the /search route is searching projects, naming the attribute project_id is redundant.

Additional context

No response