Day 5: How FormSchema Drives SQL Generation in a Definition-Driven ERP Framework

·2 views

This post explains how a new form is created in a definition-driven ERP framework using only configuration files and no code, touching six places in total. The FormSchema is the only file written from scratch, while the remaining definition files are derived from it and adjusted. The framework uses the same FormSchema to build queries, assembling joins from relationship declarations, and to build saves, producing INSERT, UPDATE and DELETE statements from the field set. Relationships are declared between forms via program identifiers rather than physical table names, which the author argues makes the design easier to change. The article illustrates this with a generated SELECT query that joins an order table to customer and employee tables.

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)

Developer Scales Privacy Directory to 215,000+ Pages in 31 Languages

A developer has built EraseRegistry.com, a programmatic directory helping users find account deletion and data removal options. The platform covers service-specific deep-links to account closure settings, difficulty ratings, and step-by-step instructions. It supports 31 languages and has grown to more than 215,000 indexable pages. The author describes treating content generation, localization, and technical SEO as one engineering pipeline, with attention to crawl budget, canonical tags, and hreflang configuration. Distribution is pursued through open-source contributions and launches on platforms such as Product Hunt and AlternativeTo rather than automated link-building.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Four brand colors from a first AI prompt survive in a developer's app

A developer reports that the four brand colors from the first AI prompt written in January still appear in the app's theme file, unchanged down to the hex codes. Most other early design choices, including the logo, the typography setup and the handling of five languages, did not survive. An August AI-proposed redesign with a calmer single-accent look was reverted because the neon palette read better, though a low-contrast purple was darkened for links. The app now uses two fonts while the website and a flyer use others, and the logo was redrawn from circles of friends to a map pin. The author also notes the AI silently dropped Romanian from the supported languages in a later prompt, which became a major challenge.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Taste-skill: a coding-agent front-end design process that measures its own output

Taste-skill is a GitHub project offering a front-end design skill for coding agents, built around a ten-stage workflow rather than a single prompt. The agent is dealt three of twenty researched design directions and must pick one, which the author argues guards against generic category defaults. An inspection script then opens the page in a real browser at three viewport widths and measures layout, fonts, colours, contrast and overflow, with failures required to be fixed. The workflow repeats critique and fixes for up to three rounds, and the final gate runs on the production build to catch differences from the dev server. The project estimates each build takes about 30 to 45 minutes and a few hundred thousand tokens, and requires Node 22 or newer plus a local Chrome. Its images must come from openly licensed collections with credits.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Guide Shows How Fitness Apps Can Enforce Consent and Account Deletion Across Systems

A DEV Community tutorial addresses a common privacy gap in fitness apps, where settings may appear to disable tracking while backend systems keep sending data. It argues that privacy controls must be enforced throughout the architecture, not just shown in the user interface. The guide covers two linked workflows: managing consent preferences and stopping optional processing when consent is withdrawn, and coordinating account deletion across services with authentication and failure handling. It describes the components involved, including the mobile app, backend, databases, analytics providers, job queues, and backup systems. The examples are illustrative and not production-ready, and legal and framework-specific requirements must be handled separately.

0 comments Read more at DEV Community