Edit a recipe for a company dish. If the dish doesn't have a recipe, a new one will be created.

This endpoint allows you to modify the default dish name (used for display purposes) and add new translations.

The ingredient and nutritional information follows these rules:

• If both ingredient_list and nutritional_indicators are provided, both are stored using the supplied values.
  In this case, auto_computed_nutritional_indicators indicates whether the nutritional information was automatically calculated.
  If this field is omitted, it defaults to false, meaning the nutritional information is considered manually provided.

• If only ingredient_list is provided, the nutritional information is automatically calculated from the valid
  LogMeal ingredients included in the recipe, and auto_computed_nutritional_indicators is set to true.
  Ingredients provided using ingredientName instead of ingredientId are not considered for this calculation.
  Only valid and existing LogMeal ingredient IDs are used.

• If only nutritional_indicators is provided, the recipe's ingredient and nutritional information is not updated.
  Nutritional indicators must be provided together with an ingredient list to apply a manual nutritional update.

The origin of ingredient and nutritional data can be specified using ingredients_source and nutrition_source.
These fields are optional and indicate how the data was obtained (for example, LogMeal database, import, or an external provider).

You can also assign a sample image to the dish, which will be associated with it for display purposes.
The image file must be in JPG or JPEG format.

The request can be sent in two formats:

• application/json: use this format when updating recipe data without uploading an image.
• multipart/form-data: serialize the recipe payload in the data field and optionally provide an image in the image field.

The JSON object contained in data follows the same structure as the application/json payload.

Legacy multipart requests that provide the recipe fields directly as form fields remain supported for backwards compatibility, but new integrations should use the data field.