Improve Method Naming for Clarity in /api/v1/foods/{id} Endpoint

[iamcymentho]

Issue Description

Problem:

In the /api/v1/foods/{id} endpoint, we currently have methods with similar names (GET, PUT, DELETE, PATCH) which can be confusing for developers, especially those who are new to developing .NET Web APIs. Clarity in method naming is essential for enhancing the project's accessibility and learning experience.

Proposal:

I propose to improve the method names in the /api/v1/foods/{id} endpoint to make them more understandable and tailored towards the action being performed. This will not only enhance the project's usability but also provide a more educational experience for developers who are new to .NET Web API development.

Action Plan:

I will work on renaming the methods in the /api/v1/foods/{id} endpoint as follows:

Change GET to GetFoodById
Change PUT to UpdateFood
Change DELETE to DeleteFood
Change PATCH to ModifyFood

These changes will align with RESTful API conventions and provide a clear and intuitive understanding of each method's purpose.

Benefits:

• Improved clarity in method names.
• Enhanced learning experience for newcomers to .NET Web API development.
• Better alignment with RESTful API conventions.

Permission Request:

I kindly request permission to work on this issue and make the proposed changes. I believe that this enhancement will benefit both the project and the community of developers using it.

[FabianGosebrink]

Hey thanks. Sure, go for it. Happy to review 🙂