Why Storing UI State in the URL Beats useState for Filters and Search

·1 views

A common bug in single-page applications causes filters, sort orders, and search queries to vanish when a user refreshes the page or shares a link, because that state is stored in component memory rather than the URL. The URL functions as a built-in, browser-native state management tool available across React, Vue, Svelte, and plain JavaScript without any extra setup. Placing shareable state — such as search queries, active filters, sort columns, and pagination — in URL query parameters automatically enables refresh survival, copy-paste sharing, and correct browser back-button behavior. Developers can use React Router's useSearchParams or libraries like nuqs for typed, serialized URL parameters with a familiar useState-style API. Ephemeral states like hover effects, tooltip visibility, or form drafts should remain in component state, while auth tokens must never be stored in the URL for security reasons.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

jsdoc-scribe CLI Gets Faster Parsing and Improved HTML in Latest Update

A developer has released a new version of jsdoc-scribe, an open-source command-line tool that automatically generates JSDoc comments and HTML documentation. The update brings faster processing, improved JavaScript and TypeScript parsing, better HTML output, and several stability fixes. The tool is available on NPM and targets developers working within modern JavaScript ecosystems. The creator aims to make jsdoc-scribe one of the most comprehensive documentation generators available and is actively seeking community feedback and contributions.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Building voice agents: latency, turn-taking, and safety trade-offs explained

A technical deep-dive on DEV Community outlines the core challenges developers face when integrating voice agents into products. The standard pipeline involves three stages — Speech-to-Text, a large language model for reasoning, and Text-to-Speech — but perceived latency, turn-taking logic, and safety guardrails determine whether the experience succeeds or fails. The article notes that the LLM stage is typically the most variable bottleneck, and that audio cues such as ambient sound or brief verbal fillers can reduce user anxiety during processing delays without actually speeding up the system. A key UX flaw highlighted is rigid turn-detection, where short user affirmations like 'yes' are misread as requests to interrupt the agent, making it feel erratic or rude. The piece concludes that balancing expressiveness, speed, and accuracy is fundamentally a product design decision before it becomes an engineering one.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

HackerRank Open-Sources ATS Code, Exposing Resume Score Inconsistency Flaws

HackerRank has open-sourced parts of its Applicant Tracking System (ATS), prompting a technical examination of how such platforms evaluate resumes. Engineers have noted that candidate scores can shift significantly — for example, between 74 and 90 — without any actual change in qualifications. These fluctuations are attributed to fragile PDF parsing, inconsistent skill taxonomy normalization, and non-deterministic NLP pipelines within the scoring engine. The core architectural problem is that the system lacks idempotency, meaning identical resume inputs can produce different scores across separate evaluations. Analysts argue this reflects a broader flaw in ATS design: attempting to reduce a candidate's complex abilities into a single numeric score introduces inherent and misleading variability.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AgentForge Offers Real-Time Structured Monitoring for AI Agent Pipelines

The AgentForge team published a post on DEV Community on June 29, 2026, arguing that traditional log-based monitoring is inadequate for modern AI agent pipelines. They contend that teams running agent workflows at scale need real-time visibility into active agents, per-agent latency, token usage, and error rates rather than after-the-fact log searches. The tool generates structured traces for every pipeline run and streams live data via WebSocket, including queue depth and cost per run. Automated alerts can trigger circuit breakers or PagerDuty notifications when error rates or latency thresholds are breached. The team has released AgentForge as an open-source MVP on GitHub to address what they see as a gap in existing agent observability tooling.

0 comments Read more at DEV Community