Update adding-fields.md

[ibrahim-embaby]

1. Clarified the Purpose of Field Resolvers

   • Updated the introduction to explicitly state that typegraphql-prisma generates GraphQL types from the Prisma schema by default.
   • Emphasized that additional fields added via @FieldResolver are not stored in the database and are computed dynamically.
   • Highlighted a key limitation: these fields cannot be used in Prisma queries for filtering or sorting.

2. Fixed Incorrect Prisma Query Syntax

   • Replaced first: 1 with take: 1 in the Prisma query.
   • Reason: Prisma does not support first, and take is the correct way to limit results when fetching related records.

3. Improved Code Readability and Structure

   • Ensured the example clearly follows best practices.
   • Kept variable names meaningful for better understanding.

4. Provided Additional Explanation

   • Added a breakdown of why @FieldResolver is necessary.
   • Explained the difference between Prisma fields and computed fields in the GraphQL schema.

These improvements make the documentation clearer, ensuring that developers understand why and how to use @FieldResolver effectively in a typegraphql-prisma project.