# zod Published articles for zod. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## LangChain: Structured Output with JavaScript DevFeed: [LangChain: Structured Output with JavaScript]() Original publisher: [Read original article]() Author: Robin Wieruch Published: 2025-01-27T06:52:46Z Content type: tutorial Language: en Sources: [Robin Wieruch]() Topics: [LangChain](), [JavaScript](), [Structured-data](), [Next.js](), [React](), [API](), [Back end](), [Front end](), [OpenAI]() Tags: [api](), [how-to](), [javascript](), [langchain](), [langchain-javascript-structured-output](), [next-js](), [react](), [schema](), [structured-output](), [validation](), [zod]() ### AI overview This tutorial demonstrates how to build structured-output responses with LangChain in JavaScript. It uses Next.js and React for the application, the OpenAI API for chatbot responses, and Zod to define and validate a shared schema between the backend and frontend. ### Source excerpt How to: Structured Output in JavaScript with LangChain. A step by step example on how to use structured data in JavaScript with LangChain ... ## React and FormData DevFeed: [React and FormData]() Original publisher: [Read original article]() Author: Robin Wieruch Published: 2024-11-11T04:50:46Z Content type: tutorial Language: en Sources: [Robin Wieruch]() Topics: [React](), [Forms](), [JavaScript](), [HTML](), [Raycast extension]() Tags: [errors](), [forms](), [how-to](), [javascript](), [library](), [react](), [react-form-data](), [schema](), [server](), [validation](), [zod]() ### AI overview This tutorial explains how to convert React FormData into a JavaScript object when submitting forms with actions. It covers concise conversion, destructuring, Zod typing and validation, and correctly handling multiple values with the same key, including checkbox and select inputs. ### Source excerpt Learn how to handle FormData in React when submitting it with a (Server) Action to the server ... ## AWS API Gateway's Request Validation: Navigating the Quirks DevFeed: [AWS API Gateway's Request Validation: Navigating the Quirks]() Original publisher: [Read original article]() Author: Thomas Klein Published: 2024-08-09T12:07:11Z Content type: tutorial Language: en Sources: [Homegate Engineering Blog - Medium]() Topics: [Amazon API Gateway](), [Amazon Web Services](), [API](), [gateway](), [JSON Schema](), [TypeScript](), [configuration](), [enum](), [HTTP]() Tags: [api](), [api-gateway](), [aws](), [aws-api-gateway](), [aws-lambda](), [enum](), [gateway](), [handler](), [http](), [json](), [json-schema](), [middleware](), [middy](), [tests](), [type-safety](), [typescript](), [validation](), [zod]() ### AI overview This tutorial examines AWS API Gateway request validation. It explains that query-parameter presence is checked, but enum values may not be enforced, while POST and PUT payloads are validated with JSON Schema Draft 4. It also discusses generic error messages and TypeScript-based validation approaches. ### Source excerpt AWS API Gateway's request validation follows a specific set of rules that developers should be aware of when setting up their APIs. While it offers some validation features, it's important to understand its scope and limitations. Let's examine how it works with a common API configuration: parameters: - name: offerType in: query required: true description: RENT or BUY schema: type: string enum: - RENT - BUY With this configuration, API Gateway diligently checks for the presence of the query parameter, returning an HTTP 400 error if it's missing. However, it falls short when it comes to validating the actual value. Surprisingly, it would accept "KERMIT" without batting an eye, despite the clear enum specification. This behavior, while documented, can be a source of frustration for developers expecting more comprehensive validation. Interestingly, API Gateway shows more validation prowess with POST and PUT requests. It validates request payloads using JSON Schema Draft 4, demonstrating a somewhat inconsistent approach to input validation across different HTTP methods. Even when it does catch an error, API Gateway's feedback is less than illuminating. Instead of specific error details, you're met with a generic {"message": "Invalid request body"}. For more information, you'll need to dig into the associated log streams, which isn't ideal for surfacing error details in API responses. Example output in AWS console from a failed request validation when a body request validator is setup. API Gateway's validation is handy, but it leaves a lot to be desired. Developers often need to add extra checks for a truly robust API. While API Gateway supports various integrations and Lambda languages, let's focus on TypeScript. TypeScript's strong typing and runtime checks can catch issues early, sparing your users from cryptic error messages. Let's explore how to use this to make your API smarter and your users happier. Option 1: DIY Validation (AKA The "I've Got Trust Issues" Approac