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.

Sign up for GitHub

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

Jump to bottom

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

Open
AlexanderHott opened this issue Apr 24, 2024 · 0 comments
Open

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

AlexanderHott opened this issue Apr 24, 2024 · 0 comments
Labels
bug For issues where things aren't working as intended

Comments

@AlexanderHott
Copy link

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
@AlexanderHott AlexanderHott added the bug For issues where things aren't working as intended label Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug For issues where things aren't working as intended
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AlexanderHott