# JSON JSON is a lightweight, language-independent data-interchange format that is easy for machines to parse and generate. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## PDFx - Extract references and metadata from PDF documents, and download all referenced PDFs DevFeed: [PDFx - Extract references and metadata from PDF documents, and download all referenced PDFs]() Original publisher: [Read original article]() Author: Chris Hager Published: 2026-09-17T02:48:44.791916Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [pdf](), [Python](), [Command-line interface](), [JSON](), [pip](), [Open Source](), [GitHub]() Tags: [apache](), [broken-links](), [command-line](), [download](), [github](), [install](), [json](), [library](), [open-source](), [pdf](), [python]() ### AI overview PDFx is an Apache-licensed open-source tool that extracts references and metadata from PDF documents. It detects PDF, URL, arXiv, and DOI references, can download referenced PDFs in parallel, identify broken hyperlinks, extract PDF text, and output results as text or JSON. It is available as a command-line tool and Python package, with support for local and online PDFs. ### Source excerpt Reading over this paper and its references recently, I thought it would be great to be able to download all the references at once... This inspired me to write a little tool to do just that, and now it's done and released under the Apache open source license: https://github.com/metachris/pdfx Features Extract references and metadata from a given PDF Detects pdf, url, arxiv and doi references Fast, parallel download of all referenced PDFs Find broken hyperlinks (using the -c flag) (more) Output as text or JSON (using the -j flag) Extract the PDF text (using the --text flag) Use as command-line tool or Python package Compatible with Python 2 and 3 Works with local and online pdfs Getting Started Grab a copy of pdfx with easy_install or pip and run it: ## Apollo Client 4.3 adds native custom scalar support and safer TypeScript types DevFeed: [Apollo Client 4.3 adds native custom scalar support and safer TypeScript types]() Original publisher: [Read original article]() Author: Jerel Miller Published: 2026-09-15T12:01:05Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [TypeScript](), [Cache](), [Caching](), [JSON]() Tags: [cache](), [graphql](), [json](), [typescript](), [upgrade]() ### AI overview Apollo Client 4.3 adds native custom scalar integration, type-safe cache access, and improved TypeScript handling for incremental GraphQL data. ### Source excerpt Apollo Client 4.3 is here: native custom scalar support, type-safe cache access, and more consistent @defer and @stream behavior. See what's new and upgrade today. ## Gson Deserialization and the InaccessibleObjectException DevFeed: [Gson Deserialization and the InaccessibleObjectException]() Original publisher: [Read original article]() Author: Marcin Buczkowski Published: 2026-09-15T05:32:46Z Content type: tutorial Language: en Sources: [Baeldung]() Topics: [Exception](), [JSON](), [Tutorial](), [Java]() Tags: [exception](), [gson](), [how-to](), [java](), [json](), [json-gson](), [tutorial]() ### AI overview This tutorial explains how Java's strong encapsulation and the Java Platform Module System can cause InaccessibleObjectException when Gson deserializes JSON through reflection. It focuses on modular projects, date handling, and Gson's maintenance status. ### Source excerpt Learn how to resolve an InaccessibleObjectException when working with Gson and modern Java versions. The post Gson Deserialization and the InaccessibleObjectException first appeared on Baeldung. ## Resolving Exception: Cannot Deserialize From Object Value (No Delegate- Or Property-Based Creator) DevFeed: [Resolving Exception: Cannot Deserialize From Object Value (No Delegate- Or Property-Based Creator)]() Original publisher: [Read original article]() Author: Martin Blažević Published: 2026-09-14T04:21:09Z Content type: tutorial Language: en Sources: [Baeldung]() Topics: [Jackson, Java Dates, Exception, LocalDate](), [Jackson](), [Exception](), [JSON]() Tags: [article](), [exception](), [how-to](), [jackson](), [jackson-exception](), [java](), [json](), [library](), [tutorial]() ### AI overview This tutorial explains why Jackson can throw InvalidDefinitionException when it cannot determine how to construct an object during JSON deserialization. It demonstrates the problem with an immutable class and presents solutions including a no-argument constructor, property-based creators using @JsonCreator and @JsonProperty, and annotated factory methods. It also notes the correct annotation package for Jackson 3.x. ### Source excerpt During JSON deserialization, Jackson may throw an InvalidDefinitionException when it can't determine how to create an instance of the target class. In this article, you'll learn how to fix this in Jackson 2.x and 3.x. The post Resolving Exception: Cannot Deserialize From Object Value (No Delegate- Or Property-Based Creator) first appeared on Baeldung. ## Policy as Code in 2026: OPA, Kyverno, Cedar and What's Next DevFeed: [Policy as Code in 2026: OPA, Kyverno, Cedar and What's Next]() Original publisher: [Read original article]() Author: Abhijit Pujare Eric Minick Published: 2026-09-11T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [policy-as-code](), [Open Policy Agent](), [rego](), [Kyverno](), [Software Engineering](), [Kubernetes](), [JSON](), [YAML](), [AI Agent]() Tags: [ai-agent](), [compliance](), [json](), [kyverno](), [opa](), [open-policy-agent](), [policies](), [policy-as-code](), [rego](), [security](), [software-engineering](), [yaml]() ### AI overview This article surveys the 2026 Policy as Code ecosystem, comparing general-purpose Open Policy Agent and Rego with specialized approaches such as Kyverno, Cedar, and agent-oriented governance. It discusses the shift toward automated, machine-readable governance, the separation of policy from business logic, and the challenges of authoring and maintaining Rego as schemas evolve. ### Source excerpt | Blog ## The thoroughness of Tom Johnson's free Documenting API's course on OpenAPI 3.0 and Swagger UI DevFeed: [The thoroughness of Tom Johnson's free Documenting API's course on OpenAPI 3.0 and Swagger UI]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-09-09T21:17:32Z Content type: article Language: en Sources: [T.J. Maher]() Topics: [OpenAPI Specification](), [Documentation](), [REST API](), [Swagger](), [Testing](), [Postman](), [JavaScript](), [JSON](), [Authentication](), [cURL](), [Chrome](), [Open Source]() Tags: [api](), [api-documentation](), [authentication](), [chrome](), [chrome-extension](), [curl](), [documentation](), [github](), [javascript](), [json](), [openapi](), [pdf](), [postman](), [rest-api](), [swagger](), [testing]() ### AI overview The article reviews Tom Johnson's free "Documenting APIs: A guide for technical writers and engineers" course. It describes the course's 17 chapters, practical API-learning exercises, coverage of REST APIs, OpenAPI, Swagger UI, testing and publishing API documentation, and a PDF edition exceeding 900 pages. ### Source excerpt While researching information for my job about the Swagger UI and how it can be used for testing, I came across this free course, called Documenting APIs: A guide for technical writers and engineers at https://idratherbewriting.com/learnapidoc/docapis_overview.html written by Tom Johnson, a technical writer based in Seattle who works for Google. The course looks intense, containing 17 chapters talking about Introduction to REST APIs, using APIs like a developer, Documenting API endpoints, the Open API spec, Testing API docs, Publishing API docs, and more. From the Course Introduction: "You'll first learn about API documentation by using a simple weather API to put a weather forecast on your site. [...] As you use the API, you'll learn about endpoints, parameters, data types, authentication, curl, JSON, the command line, Chrome's Developer Console, JavaScript, and more. The idea is that rather than learning about these concepts independent of any context, you learn them by immersing yourself in a real scenario while using an API. Immersion in real scenarios makes these tools and technologies more meaningful. "We'll then transition into standards, tools, and specifications for REST APIs. You'll learn about the required sections in API documentation, analyze examples of REST API documentation from various companies, learn how to join an open-source project to get experience, and more. "[...] We'll also dive into specifications such as the OpenAPI specification and Swagger UI (which provides tooling for the OpenAPI specification). Additionally, you'll learn how to document native library APIs and generate Javadoc". Tom Johnson offers a PDF version of this free course... over 900 pages, with more always being added. It also offers many workshop-like activities you could put in an actual itinerary. You would need for the course: Chrome, since it provides "a Javascript Console that works well for inspecting JSON", the JSON Formatter Chrome extension, Postman, a GitHub acco ## Patching This Site's MCP Endpoint and Limiting What It Can Do DevFeed: [Patching This Site's MCP Endpoint and Limiting What It Can Do]() Original publisher: [Read original article]() Author: Brent Leekley Published: 2026-09-08T00:00:00Z Content type: tutorial Language: en Sources: [brent.leekley.me blog]() Topics: [Model Context Protocol](), [MCP Server](), [API](), [HTTP](), [JSON]() Tags: [aeo](), [agent-ready-website](), [agentic-ai](), [agents](), [api](), [api-security](), [clients](), [json-rpc](), [logs](), [mcp](), [mcp-server](), [model-context-protocol](), [prompt-injection](), [protocol](), [rate-limiting](), [retry](), [server](), [streamable-http](), [webmcp]() ### AI overview This article explains how to patch a website's public, unauthenticated MCP endpoint. It covers updating to the current protocol revision while retaining compatibility with older clients, and applying limits including read-only tools, per-IP rate limiting, request-size caps, Origin checks, POST-only access, non-reflected strings, and privacy-preserving logs. ### Source excerpt An MCP server on your website is a public, unauthenticated API. Bringing one to the current protocol revision while keeping older clients working, and the seven limits that bound it: read-only tools, a per-IP rate limit that always sends Retry-After, hard caps on body and argument size, an https-only Origin check, POST only, no reflected strings, and logs that store a salted hash instead of an address. ## When JSONB columns create schema, consistency, and performance problems DevFeed: [When JSONB columns create schema, consistency, and performance problems]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-09-01T00:00:00Z Content type: article Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [data](), [Structured-data](), [JSON]() Tags: [data-modelling](), [indexing](), [jsonb](), [migration](), [outage](), [postgres](), [postgresql](), [query](), [schema](), [schema-design](), [toast]() ### AI overview The article explains why using JSONB to avoid recurring migrations can create hidden schema and data-consistency problems. It discusses runtime failures from inconsistent keys and types, difficulty identifying dependencies across consumers, and the storage and update costs of large PostgreSQL JSONB documents. ### Source excerpt JSONB is a good fit for genuinely open-ended data and a poor one for schema you did not want to commit to yet. Without a schema there is no NOT NULL, no type, no foreign key and no way to know which keys are load bearing, so every read becomes a parse and a cast that can fail at runtime. Large documents are stored out of line and compressed, which means reading one key can require fetching and decompressing the whole document, and updating one key rewrites all of it. ## Benchmarking Go 1.27's New JSON API Against the Legacy Implementation DevFeed: [Benchmarking Go 1.27's New JSON API Against the Legacy Implementation]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-08-29T18:33:33Z Content type: opinion Language: en Sources: [Daniel Lemire]() Topics: [Go Language](), [JSON](), [Programming]() Tags: [go](), [json](), [performance](), [release]() ### AI overview The article benchmarks Go 1.27's new JSON engine and APIs against the original implementation across several documents and operations. Results vary by workload: the new API generally improves unmarshalling and can substantially improve marshalling, but the legacy implementation remains faster for some structured data cases. ### Source excerpt JSON is a standard format for data interchange. It is effectively a tiny subset of JavaScript made of objects and arrays. It looks as follows {"key":1, "text":[1.0,2.0]}. Many programming languages include a JSON library in their standard libraries: C#, Go, Java (soon), Python, JavaScript, etc. The Go implementation is convenient, but not especially fast. Go ... Continue reading The new Go JSON API: twice as fast, or 1.5x slower? ## Vercel CLI expands commands for DNS, domains, and projects DevFeed: [Vercel CLI expands commands for DNS, domains, and projects]() Original publisher: [Read original article]() Author: Melkey Moksyakov Published: 2026-08-28T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [Terminal](), [API](), [dashboards](), [observability](), [JSON]() Tags: [agents](), [api](), [cli](), [configuration](), [dns](), [json](), [observability](), [projects](), [terminal](), [update](), [vercel](), [web]() ### AI overview Vercel CLI adds commands for managing DNS records, Vercel domains, project state, observability settings, and project members. The commands support structured JSON output and require explicit confirmation for billable or destructive actions. ### Source excerpt The Vercel CLI now provides dedicated commands for managing DNS records, domains, and projects. This brings more of the functionality available through the Vercel dashboard and API to the terminal, where it can be used interactively, in scripts, or by agents. Inspect and update DNS records Retrieve the complete configuration for a DNS record or update it in place using its record ID. vercel dns update supports changes to the record name, type, value, TTL, MX priority, and comment. SRV records can also be updated using their priority, weight, port, and target fields. Renew domains bought on Vercel Renew a domain on demand or control whether it renews automatically. The renewal command displays the current renewal price and asks for confirmation before completing the purchase. Control project state and observability Pause or resume a project and configure its observability features directly from the CLI. Web Analytics and Speed Insights could already be enabled from the CLI; they can now be disabled as well. Add and remove project members Add a project member with a specific role or remove an existing member. All of the new commands support structured JSON output for scripts and agents. Billable or destructive actions require explicit confirmation. Update to version 59.6.2 (or later) of the Vercel CLI to use the new commands: Learn more in the Vercel CLI documentation. Read more ## Vercel Security Dashboard is now generally available DevFeed: [Vercel Security Dashboard is now generally available]() Original publisher: [Read original article]() Author: Jathin Singaraju Published: 2026-08-26T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [dashboards](), [Security](), [Vercel](), [Command-line interface](), [OpenID connect (OIDC)](), [Terminal](), [ci](), [CSV](), [JSON]() Tags: [ci](), [cli](), [coding-agents](), [documentation](), [git](), [json](), [oidc](), [report](), [scope](), [security](), [terminal](), [ui](), [vercel]() ### AI overview Vercel Security Dashboard is generally available on all plans. It centralizes security findings across accounts and projects, supports risk-ordered remediation and CSV export, and provides equivalent checks through the Vercel CLI. Agents can inspect findings, apply supported fixes, and re-check results, with JSON output available in CI and other non-interactive environments. ### Source excerpt The Vercel Security Dashboard is now generally available on all plans, giving you one place to see your security posture across every account and project. You can access the Security Dashboard in the UI or run vercel security check in the Vercel CLI. As teams grow and coding agents make it faster to spin up projects, small misconfigurations add up quietly. The Security Dashboard automatically flags issues like: Team members without 2FA Long-lived credentials that can be replaced with OIDC Public preview deployments Non-sensitive and stale environment variables The Security Dashboard UI Misconfigurations are ordered by risk with the most severe first, and each finding links to the settings that fix them. Findings that are just noise for your team can also be muted, and all results can be exported to a CSV file for triage or reporting. The Security Dashboard CLI You can also run the same checks in your terminal through the new Vercel CLI vercel security check command, allowing your agents to work through the findings for you. An agent using vercel security check --findings can read what failed, apply the fix and re-check to confirm. Fixes an agent can apply include: Turning on Git fork protection Marking an environment variable as sensitive Replacing a static credential with OIDC federation You can also scope the check to one project with --project when you want a narrow change set. In CI or any other non-interactive environment, the command writes the report to stdout as JSON automatically, giving agents structured output without extra flags. Get started by running your first scan from the Security Dashboard, and learn more in the Security Dashboard documentation. Read more ## Pulumi Context API: query your infrastructure as a graph DevFeed: [Pulumi Context API: query your infrastructure as a graph]() Original publisher: [Read original article]() Author: Levi Blackstone Published: 2026-08-26T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [API](), [Graphs](), [Cloud APIs](), [infrastructure as code (IAC)](), [Command-line interface](), [JSON](), [pulumi-neo]() Tags: [agent](), [ai-agents](), [api](), [cli](), [features](), [graph](), [iac](), [infrastructure-as-code-iac](), [json](), [product](), [pulumi](), [pulumi-cloud](), [pulumi-neo](), [rest-api]() ### AI overview Pulumi is launching the Context API, a read-only API that connects Pulumi-managed and discovered resources, stacks, and their relationships into a graph. Available in public preview for Enterprise and Business Critical organizations, it supports infrastructure-impact, coverage, and cleanup queries through the Pulumi CLI or REST API. Pulumi Neo uses it out of the box, and other authenticated agents can access its schema and query guidance. ### Source excerpt Every platform team fields the same questions: What is running? What breaks if we change this? What can we safely delete? The answers exist, but they're scattered across state files, cloud consoles, and the memories of whoever set things up. Today we're launching the Pulumi Context API, a read-only API that connects Pulumi-managed and discovered resources, stacks, and their relationships into a graph. It's designed agent-first: Pulumi Neo, our infrastructure agent, uses it out of the box, and other agents can fetch the current graph vocabulary and query guidance on demand. It's available in public preview for organizations on the Enterprise and Business Critical editions. Answers that follow infrastructure relationships Pulumi already records the resources your programs manage, their dependencies, how stacks consume each other's outputs, and the resources Pulumi Discovery finds outside infrastructure as code (IaC). The Context API connects this data so you can ask questions that depend on the relationships: Impact: Which stacks are affected if we upgrade this provider? If this stack changes, what consumes its outputs? Coverage: How much of our infrastructure lives outside IaC, and in which accounts? Cleanup: Which stacks have no dependents and are candidates for retirement? A query is a JSON document with a handful of clauses. anchor names the starting nodes, traverse follows relationships from there, and return chooses what comes back. You can run a query through the Pulumi CLI or REST API. Here's a selector that starts from AWS provider instances older than version 7.0.0 and follows incoming provided_by relationships back to the visible resources they manage: { "anchor": { "nodeType": "resource", "match": { "type": "pulumi:providers:aws", "fields": { "provider_version": { "op": "lt", "value": "7.0.0" } } } }, "traverse": [ { "edgeTypes": ["provided_by"], "direction": "in", "alias": "managed" } ], "return": { "select": ["anchor", "managed"] } } A response for one m ## Keeping Documentation Honest with an OpenAPI Snapshot Diff DevFeed: [Keeping Documentation Honest with an OpenAPI Snapshot Diff]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-25T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [OpenAPI Specification](), [FastAPI](), [ci](), [Pytest](), [Documentation](), [JSON](), [test]() Tags: [api-documentation](), [ci](), [ci-cd](), [documentation](), [fastapi](), [json](), [openapi](), [pytest](), [test](), [testing]() ### AI overview The article explains how to keep API documentation aligned with a FastAPI application by generating its OpenAPI schema from the running code, comparing it with a committed snapshot in CI, normalizing the JSON diff, and requiring deliberate snapshot regeneration. ### Source excerpt FastAPI app.openapi() snapshot test in pytest: fail CI when the live OpenAPI schema drifts from the committed openapi.snapshot.json. ## How to Fix Jackson JSON Parse Error Can not construct instance of java.time.LocalDate DevFeed: [How to Fix Jackson JSON Parse Error Can not construct instance of java.time.LocalDate]() Original publisher: [Read original article]() Author: Hiks Gerganov Published: 2026-08-22T23:26:23Z Content type: tutorial Language: en Sources: [Baeldung]() Topics: [Jackson, Java Dates, Exception, LocalDate](), [LocalDate](), [JSON](), [Exception](), [ISO 8601](), [Code]() Tags: [code](), [errors](), [exception](), [how-to](), [jackson](), [jackson-java-dates-exception-localdate](), [java](), [java-dates](), [json](), [learn](), [localdate](), [post](), [time](), [types]() ### AI overview This tutorial explains why Jackson may fail to deserialize JSON date values into Java's LocalDate or LocalDateTime, even when the JSON uses ISO-8601 formatting. It examines Jackson version support, missing Java Time module configuration, unsupported date formats, and mismatched date-time types, then presents ways to address the problem. ### Source excerpt Learn why sometimes Jackson can't construct an instance of LocalDate or LocalDateTime and how to fix the error it throws. The post How to Fix Jackson JSON Parse Error Can not construct instance of java.time.LocalDate first appeared on Baeldung. ## Java Weekly, Issue 660 DevFeed: [Java Weekly, Issue 660]() Original publisher: [Read original article]() Author: baeldung Published: 2026-08-22T11:26:18Z Content type: article Language: en Sources: [Baeldung]() Topics: [API](), [JSON](), [Quarkus](), [Gradle](), [Retrieval Augmented Generation (RAG)](), [Amazon Bedrock](), [agent observability]() Tags: [amazon-bedrock](), [api](), [gradle](), [java](), [json](), [no-ads](), [no-after-post](), [no-before-post](), [no-optins](), [rag](), [release](), [weekly-review](), [weekly-review-no-ads-no-after-post-no-before-post-no-optins]() ### AI overview Java Weekly, Issue 660 is a roundup of Java ecosystem news, including a Hibernate second-level cache performance case study, a proposed small JSON API for JDK 28, Gradle and Renovate integration, AI and RAG resources, and recent Quarkus and other library releases. ### Source excerpt A clear Hibernate speedup and a new JSON API coming to Java. The post Java Weekly, Issue 660 first appeared on Baeldung. ## Tips for Saving Game Data in Godot DevFeed: [Tips for Saving Game Data in Godot]() Original publisher: [Read original article]() Published: 2026-08-21T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Godot](), [saving](), [Concurrent Programming](), [data](), [JSON](), [Hardware](), [Testing]() Tags: [bug](), [code](), [disk-space](), [game](), [games](), [json](), [mutex](), [os](), [saving](), [testing](), [thread](), [tips]() ### AI overview This tutorial describes a save-data approach for Godot games, based on experience shipping two games. It compares custom binary and JSON formats, recommends frequent debounced saves on a separate thread, checks available disk space, and discusses temporary-file replacement to reduce corrupted save-game reports. ### Source excerpt Saving game data is easy. Making your save code survive every kind of hardware failure is not. A lot of these issues will never show up during testing, but if your game reaches a wide audience with many different kinds of hard drives in different states of degradation, you will start to get bug reports about save games not working. I decided to write up my approach, learned over the course of shipping two Godot games, that has reduced our corrupted save game bug reports to virtually nothing. ## Develop and test MCP in Postman: jhipster-mcp in action DevFeed: [Develop and test MCP in Postman: jhipster-mcp in action]() Original publisher: [Read original article]() Author: Anthony Viard Published: 2026-08-19T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [Model Context Protocol](), [Postman](), [Spring Boot](), [Node.js](), [TypeScript](), [Angular](), [React](), [Vue.js](), [JSON](), [Remote Procedure Call (RPC)]() Tags: [ai-agents](), [angular](), [apache](), [cli](), [general](), [jhipster](), [json](), [mcp](), [node-js](), [open-source](), [post](), [react](), [rpc](), [spring-boot](), [typescript](), [vue]() ### AI overview This Postman developer article demonstrates jhipster-mcp, an open-source MCP server that exposes the JHipster generator to MCP clients. It uses Postman's MCP client to test tools, prompts, and resources for generating and evolving Spring Boot applications from JDL. ### Source excerpt Drive the jhipster-mcp server from Postman's MCP client to test tools, prompts, and resources before handing them to an AI agent. Try it today. The post Develop and test MCP in Postman: jhipster-mcp in action appeared first on Postman Blog. ## Reconciling JSON in DuckDB, One Patch at a Time DevFeed: [Reconciling JSON in DuckDB, One Patch at a Time]() Original publisher: [Read original article]() Author: {"picture" =\> "/images/blog/authors/mustafa\_khan\_atlan.jpg"} Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [DuckDB]() Topics: [JSON](), [Databases](), [data](), [SQL](), [Benchmark](), [Python]() Tags: [benchmark](), [data](), [duckdb](), [extension](), [json](), [python](), [sql]() ### AI overview DuckDB v2.0 expands its JSON extension with functions for computing inverse RFC 7396 merge patches, applying patches with skip-on semantics, canonicalizing key order, and recursively removing null-valued keys. The article demonstrates how these functions support JSON reconciliation in SQL and compares them with Python implementations using synthetic CDC events. ### Source excerpt DuckDB v2.0 will ship JSON functions that allow you to easily apply JSON patches. ## Building Tactile UX: Honoring Intentional Design With Lottie DevFeed: [Building Tactile UX: Honoring Intentional Design With Lottie]() Original publisher: [Read original article]() Author: hello@smashingmagazine.com (Alexey Kopytin) Published: 2026-08-11T10:00:00Z Content type: article Language: en Sources: [Articles on Smashing Magazine -- For Web Designers And Developers]() Topics: [User experience (UX)](), [Front end](), [Web](), [Document Object Model (DOM)](), [real-time](), [math](), [JSON](), [Matter]() Tags: [animation](), [article](), [design](), [developers](), [json](), [real-time](), [ui](), [ux](), [vector](), [web](), [web-interface]() ### AI overview This article explains how Isadora Agency built Stress Release, a tactile digital stress-relief squeeze toy, using intentional Lottie animations, DOM events, and distance-based math instead of a physics engine. It focuses on deterministic, frame-accurate animation control and describes mapping DOM interactions to Lottie states rendered as JSON-based SVG animations. ### Source excerpt When tasked with building a highly interactive, tactile web experience, the architecture must serve the art direction. In this article, Alexey Kopytin explains their architectural rationale for building a digital stress-relief squeeze toy game using Lottie animations, DOM events, and distance-based math to maintain absolute control over their designers' intentional motion. ## Claude Code statusline: model name and context usage at a glance DevFeed: [Claude Code statusline: model name and context usage at a glance]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2026-08-11T10:00:00Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [Claude Code](), [context window](), [JSON](), [Terminal](), [Code]() Tags: [claude-code](), [code](), [context-window](), [json](), [terminal]() ### AI overview A tutorial on configuring a Claude Code terminal statusline that reads the JSON payload supplied to a statusline script. The resulting bar displays the project and branch, current model, and color-coded context usage with token counts. ### Source excerpt Claude Code pipes a JSON payload into your statusline script. Read it, and the bar shows the project and branch you are on, the model, and color-coded context usage with token counts. ## The Appwrite CLI is now written in Go DevFeed: [The Appwrite CLI is now written in Go]() Original publisher: [Read original article]() Author: Chirag Aggarwal Published: 2026-08-11T00:00:00Z Content type: article Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Command-line interface](), [Go Language](), [npm](), [TypeScript](), [JSON]() Tags: [announcements](), [cli](), [dependencies](), [go](), [json](), [npm](), [packages](), [typescript]() ### AI overview Appwrite rewrote its CLI from TypeScript and Node to Go while preserving the command surface, flags, exit codes, and JSON output. Measurements reported in the article show lower startup time, installation size, memory use during push, and binary size. ### Source excerpt The Appwrite CLI moves from TypeScript to Go. It starts 17 times faster and installs two packages in place of 330. Every flag, exit code, and byte of JSON output stays the same. ## Generating AI Descriptions of Automated Pull Requests DevFeed: [Generating AI Descriptions of Automated Pull Requests]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2026-08-11T00:00:00Z Content type: tutorial Language: en Sources: [Daniel Doubrovkine]() Topics: [GitHub Copilot CLI](), [GitHub Actions](), [GitHub Copilot](), [Large Language Model](), [Ruby](), [Slack](), [changelog](), [Pull Request](), [Open Source](), [JSON](), [YAML]() Tags: [ai](), [automated](), [changelog](), [ci](), [cli](), [copilot](), [github](), [github-actions](), [github-copilot](), [github-copilot-cli](), [json](), [llm](), [open-source](), [pull-request](), [pull-requests](), [ruby](), [yaml]() ### AI overview A tutorial explains how the maintainer of the slack-ruby-client library uses a scheduled GitHub Actions workflow and GitHub Copilot CLI to generate meaningful commit messages, pull request bodies, and CHANGELOG entries from diffs of regenerated Slack API code. It also covers YAML indentation, prompt files, response logging, and extracting a JSON result from Copilot CLI output. ### Source excerpt The slack-ruby-client library, an open source Ruby gem I maintain, runs a scheduled GitHub Actions workflow that regenerates code from Slack's API definitions and opens a pull request with the diff. The commit message and CHANGELOG entry used to be a generic "Update API (2026-08-11)", which told a reviewer nothing about what actually changed. Here's how we taught the workflow to describe its own diffs, using GitHub Copilot CLI, which open source maintainers can get for free. The Idea The workflow already computes a diff before opening the pull request. Instead of a boilerplate commit message, we pipe that diff through an LLM and ask it to summarize what changed, then use the response as the commit message and PR body. - name: Check for changes id: changes run: | if git diff --quiet; then echo "changed=false" >> "$GITHUB_OUTPUT" else echo "changed=true" >> "$GITHUB_OUTPUT" fi - name: Prepare diff for AI summary if: steps.changes.outputs.changed == 'true' run: | git diff --stat | sed 's/^/ /' > /tmp/diff_stat.txt git diff | head -c 20000 | sed 's/^/ /' > /tmp/diff.txt The sed 's/^/ /' indent isn't decorative. actions/ai-inference substitutes template variables as raw text into a prompt YAML file before parsing it, so a multi-line diff starting at column 0 breaks the indentation of the enclosing content: |- block scalar. Pre-indenting the file to match keeps the YAML valid no matter what the diff looks like. The Prompt File actions/ai-inference supports .prompt.yml files, a small convention for keeping the system/user prompt out of the workflow YAML. messages: - role: system content: |- You write CHANGELOG entries describing an automated API update to slack-ruby-client, a Ruby gem whose Web API endpoint methods, argument validations, specs, and bin commands are code-generated from vendored Slack API method definitions (via a git submodule and rake task). Given a diffstat and a diff of the regenerated files, respond with ONLY a single JSON object (no markdown code fence ## How to build a Gemini content assistant that belongs inside your Webflow CMS DevFeed: [How to build a Gemini content assistant that belongs inside your Webflow CMS]() Original publisher: [Read original article]() Author: Ismail Ajagbe Published: 2026-08-08T00:00:00Z Content type: tutorial Language: en Sources: [Webflow Blog]() Topics: [Content Management System](), [webflow](), [Google AI](), [Next.js](), [API](), [JSON](), [Streaming](), [Node.js]() Tags: [api](), [gemini](), [google-ai](), [guides](), [how-to](), [json](), [next-js](), [node-js](), [streaming](), [webflow]() ### AI overview A tutorial for building a Gemini-powered content assistant inside Webflow CMS using Webflow Cloud, Next.js, and the Gemini API. It covers streaming drafts for open-ended writing and a JSON mode that returns content mapped to CMS fields. ### Source excerpt Learn how to build a Gemini content assistant on Webflow Cloud that streams drafts and returns CMS-ready JSON. ## SCIM Deprovisioning Is a Promise Your App Probably Breaks DevFeed: [SCIM Deprovisioning Is a Promise Your App Probably Breaks]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-06T01:29:36Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Security](), [API](), [HTTP](), [JSON](), [Internet Engineering Task Force (IETF)](), [Protocol (disambiguation)]() Tags: [api](), [http](), [identity](), [idp](), [ietf](), [json](), [net-conf](), [protocol](), [schema](), [security](), [standards](), [state](), [token]() ### AI overview This article explains that SCIM deprovisioning updates identity state but does not automatically invalidate an application's sessions, refresh tokens, or API keys. It describes how identity providers commonly use soft deactivation and why applications must explicitly handle the resulting offboarding state. ### Source excerpt SCIM tells you a user is gone, but sessions, refresh tokens, and API keys often outlive deprovisioning. Here's why offboarding needs more than a user row. [Next page]()