Allowing end-users to define custom fields when requesting data from your application programming interface (API) endpoints is inevitable. When you're exposing data through a REST API (for instance, a products database), it might contain many fields like `product_id`, `product_name`, `retail_price`, `discount`, `category_name`, `reviews`, `ratings` and `related_products`. However, your data consumers may not require a response from all those fields when displaying data in their custom user inter......