如何在Yesod中操作JSON数据及修改POST请求JSON的age并返回

Hey there! Let’s break this down step by step—since you’re new to both Haskell and Yesod, we’ll cover the basics of handling JSON in Yesod first, then walk through modifying the age field in your POST request response.

Yesod works seamlessly with the aeson library (Haskell’s go-to for JSON processing), so we’ll start with setting up type-safe JSON parsing/serialization, which is the Haskell way to avoid common bugs.

First, you’ll need a few language extensions and imports at the top of your handler file:

{-# LANGUAGE DeriveGeneric     #-}
{-# LANGUAGE DeriveAnyClass    #-}
{-# LANGUAGE OverloadedStrings #-}

import GHC.Generics
import Data.Aeson
import Yesod

Next, define a Haskell data type that matches the structure of your incoming JSON. We’ll use DeriveGeneric and DeriveAnyClass to let aeson automatically generate JSON parsing/serialization logic for us:

data Person = Person
  { name :: String
  , age  :: Int
  } deriving (Show, Generic, FromJSON, ToJSON)

• FromJSON: Lets Yesod convert incoming JSON into a Person value
• ToJSON: Lets Yesod convert a Person value back into JSON for responses

Let’s create an endpoint that accepts a JSON Person, modifies the age field, and returns the updated JSON.

Step 1: Add the Route #

Open your config/routes file and add this line to define the POST endpoint:

POST /modify-age ModifyAgeR

Yesod automatically maps this route to a handler function named postModifyAgeR (the post prefix indicates it’s a POST request).

Step 2: Write the Handler Function #

In your handler module (e.g., Handler/Home.hs), add this function:

postModifyAgeR :: Handler Value
postModifyAgeR = do
  -- Parse the incoming JSON request body into a Person value
  -- This automatically returns a 400 error if the JSON doesn't match the Person structure
  incomingPerson <- requireCheckJsonBody :: Handler Person

  -- Modify the age field (example: increment by 1, or any logic you need)
  let updatedPerson = incomingPerson { age = age incomingPerson + 1 }

  -- Convert the updated Person back to JSON and send it as the response
  return $ toJSON updatedPerson

Alternative: Modify JSON Directly (Without a Data Type) #

If you don’t want to define a full data type (though type safety is recommended), you can work directly with aeson’s Value type to tweak the age field:

postModifyAgeR :: Handler Value
postModifyAgeR = do
  incomingJson <- requireCheckJsonBody :: Handler Value

  -- Update the "age" field if it exists (example: multiply by 2)
  let updatedJson = case incomingJson of
        Object obj -> Object $ obj & at "age" %~ fmap (\n -> n * 2 :: Int)
        _ -> incomingJson -- Return unchanged if it's not a JSON object

  return updatedJson

Since you’re new to both, here are common pitfalls to watch for:

• Forgotten Language Extensions: The DeriveGeneric, DeriveAnyClass, and OverloadedStrings extensions are mandatory for the code above—don’t skip them!
• Route-Handler Mismatch: Yesod uses naming conventions: POST routes map to post[RouteName]R, GET maps to get[RouteName]R. Double-check your function name matches the route.
• Dependency Issues: Make sure your cabal or stack file includes dependencies for yesod and aeson:

  build-depends:
    base >= 4.14 && < 5,
    yesod >= 1.6,
    aeson >= 2.0
  

To answer your final question: Your issue likely combines both Yesod-specific knowledge (route setup, request/response handling) and Haskell basics (data types, record syntax, language extensions). Taking it step by step like this should help you untangle both!

内容的提问来源于stack exchange，提问作者Rafael Klynger