Solon Framework Offers Lightweight I18n Module With Three Built-In Locale Resolvers

·1 views

The Solon Java framework has introduced an internationalization (i18n) module designed to eliminate boilerplate configuration typically associated with localization setups. The module relies on three built-in locale resolvers — header-based, cookie-based, and session-based — along with a single annotation and a utility class. Developers place standard Java properties files under a resources/i18n directory, and Solon discovers them automatically without requiring bean declarations or XML configuration. For cases where the built-in resolvers are insufficient, the framework allows custom resolver implementation via the LocaleResolver interface. Template engines including Freemarker, Thymeleaf, Beetl, and Enjoy are supported through the @I18n annotation, which injects an i18n variable directly into views.

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)

Why Local Dev Setup Matters: Env Vars, Docker, and Avoiding Hardcoded Secrets

A software engineering explainer uses a mentor-nephew dialogue to highlight common mistakes developers make during local development setup. The core lesson warns against hardcoding credentials like database passwords directly in source code, since once committed to Git, they remain in repository history permanently. The recommended fix is storing sensitive configuration in a .env file excluded from version control, allowing the same codebase to connect to different environments without code changes. The episode also cautions against using lightweight database substitutes like SQLite locally when production runs PostgreSQL, as subtle differences in constraint and query behavior can cause bugs that only surface in staging. Tools like Docker Compose are presented as a practical way to run the same database engine locally, improving consistency between development and production environments.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Same fabricated RAG answer scored 0.0 by RAGAS and 1.0 by DeepEval in faithfulness test

A developer building AI tools for healthcare discovered that two widely used LLM-based faithfulness metrics, RAGAS and DeepEval, produced opposite scores when evaluating the same fabricated output from a RAG system. In a controlled experiment using 27 outputs and five repeated runs each, RAGAS correctly flagged the hallucination while DeepEval awarded a perfect score, even praising the answer for accuracy. To address reliability concerns in high-stakes medical applications, the developer built OpenGATE, a deterministic evaluation framework that checks for required facts, numeric traceability, and appropriate abstention without relying on a grader model. Comparative testing showed LLM judges hold a clear advantage in detecting meaning inversions, while deterministic checks proved more consistent for catching omissions and fabricated numbers. The author concludes that neither approach alone is sufficient, recommending a hybrid evaluation strategy combining LLM judges with deterministic checks for production-grade AI systems.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Zustand Is Replacing Redux and Context API in Enterprise React Apps

State management in React has long been dominated by Redux, but its complexity and boilerplate have pushed developers toward lighter alternatives. React's Context API, while popular, causes performance issues in enterprise apps through unnecessary re-renders and deeply nested provider trees. Zustand, a minimalist subscription-based library, addresses these problems by storing state outside React's render cycle and letting components subscribe only to the specific data slices they need. Using patterns like domain-based store slices and selectors, teams can build scalable, high-performance applications with far less code. Developers at Smart Tech Devs report adopting Zustand in React and Next.js projects to avoid the pitfalls of both Redux and Context.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

True anonymous surveys require data inventory, not just removing name fields

Building a genuinely anonymous survey demands a systematic audit of every data point that enters, persists in, or leaves a system — not merely omitting a name field. Developers at CandorKit, a short-lived survey tool, outlined a framework that labels each collected value as required, optional, or prohibited for a given task. The platform avoids storing names, account IDs, IP addresses, and cookies alongside responses, instead hashing owner keys and using URL fragments that browsers do not transmit in standard HTTP requests. However, the team notes that network providers, small group sizes, unique events, and free-text answers can still expose respondents even when identity columns are absent from the database. The core principle is subtractive design: systematically removing identity paths, limiting data retention to defined expiry windows, and clearly communicating what anonymity guarantees do and do not cover.

0 comments Read more at DEV Community