--- title: "ThaSha (@thasha) | Hashnode" description: "ThaSha (@thasha) writes on Hashnode. Read their latest articles and follow their work." url: "https://hashnode.com/@thasha" --- @thasha # ThaSha @thasha · Joined February 2026 ### [RFC 7807 Error Responses in DataWeave: One Transform for All Endpoints](https://thasha.hashnode.dev/rfc-7807-error-responses-in-dataweave-one-transform-for-all-endpoints?utm_source=hashnode&utm_medium=feed) Our API had 14 endpoints and 14 different error response formats. The mobile team spent 3 days writing separate error parsers for each one. I standardized everything to RFC 7807 with one DataWeave transform. TL;DR RFC 7807 defines a standard error f... 3 min read · [thasha.hashnode.dev](https://thasha.hashnode.dev/rfc-7807-error-responses-in-dataweave-one-transform-for-all-endpoints?utm_source=hashnode&utm_medium=feed) [Apr 13](https://hashnode.com/posts/rfc-7807-error-responses-in-dataweave-one-transform-for-all-endpoints/69dc32d8914153b955d732e7) ### [DataWeave partition() for Bulk API Responses](https://thasha.hashnode.dev/dataweave-partition-for-bulk-api-responses?utm_source=hashnode&utm_medium=feed) Our bulk import API returned 200 OK on every request. Nobody noticed that 40% of records were failing silently for 3 days. TL;DR partition() from dw::core::Arrays splits an array into success/failure groups in one pass Build summary (total, succeede... 3 min read · [thasha.hashnode.dev](https://thasha.hashnode.dev/dataweave-partition-for-bulk-api-responses?utm_source=hashnode&utm_medium=feed) [Apr 12](https://hashnode.com/posts/dataweave-partition-for-bulk-api-responses/69db146ac10bae8d905064eb) ### [Parsing LLM Responses in DataWeave: 3 Layers of Defense](https://thasha.hashnode.dev/parsing-llm-responses-in-dataweave-3-layers-of-defense?utm_source=hashnode&utm_medium=feed) I connected MuleSoft to GPT-4o last quarter for a support ticket classifier. The prompt builder worked (I covered that in a previous post). The LLM call worked. Then the response came back and my parser crashed. The LLM was supposed to return clean J... 5 min read · [thasha.hashnode.dev](https://thasha.hashnode.dev/parsing-llm-responses-in-dataweave-3-layers-of-defense?utm_source=hashnode&utm_medium=feed) [Apr 5](https://hashnode.com/posts/parsing-llm-responses-in-dataweave-3-layers-of-defense/69d2c38139f2e052e736edef) ### [Building LLM Prompts From Enterprise Data in DataWeave](https://thasha.hashnode.dev/building-llm-prompts-from-enterprise-data-in-dataweave?utm_source=hashnode&utm_medium=feed) I connected a MuleSoft API to an LLM last quarter for a support ticket classifier. The API call was easy — the MuleSoft AI Connector handles that. Building the prompt payload from enterprise data? That's where I spent 2 hours debugging escape sequenc... 3 min read · [thasha.hashnode.dev](https://thasha.hashnode.dev/building-llm-prompts-from-enterprise-data-in-dataweave?utm_source=hashnode&utm_medium=feed) [Apr 5](https://hashnode.com/posts/building-llm-prompts-from-enterprise-data-in-dataweave/69d2b193aef1b763bc2cd29e) ### [DataWeave Runtime Type Detection: Auto-Discover Schema Mismatches](https://thasha.hashnode.dev/dataweave-runtime-type-detection-auto-discover-schema-mismatches?utm_source=hashnode&utm_medium=feed) I built a schema discovery function for a 6-system integration last year. Each source sent different types for the same fields. One function auto-detects types at runtime and builds a complete schema. TL;DR describeType function uses is operator cha... 3 min read · [thasha.hashnode.dev](https://thasha.hashnode.dev/dataweave-runtime-type-detection-auto-discover-schema-mismatches?utm_source=hashnode&utm_medium=feed) [Apr 5](https://hashnode.com/posts/dataweave-runtime-type-detection-auto-discover-schema-mismatches/69d29f36b224c93286d5e981)