There was an error while loading. Please reload this page.
📝 docs: the visual editor page catches up with the editor The page was written when there was a preview and an identity mechanism and nothing else, and it has been saying "no editing from the canvas" through four slices that added exactly that. Nothing compiles a wiki, so a stale page stays green forever and the site publishes it. Now documented, EN and pt-BR: the three tiers a selected node is classified into and why they exist (a row built five hundred times in a foreach has one source site and no separate existence, so "delete this row" is wrong for it); the inspector, its three honesty rules — compiled before offered, WorkspaceEdit rather than a file write, never rewriting the form the file is written in — and the one level it descends so that padding and background are reachable at all; and the three structural gestures with the fence they live inside. The distinction the whole design turns on is now stated rather than implied: UNDERSTANDING is not fenced, only WRITING is. The editor opens code that already exists, and real code splits itself across helper methods and files. Both Roadmap pages carried a premise the work disproved on day one — that click-to-select would ride the V3 source maps eqc already emits. It cannot: the whole Build body is emitted through one call, so the finest position a map can name is the start of the method. The repo's ROADMAP said so; the wiki went on telling readers the opposite.
📝 docs: the model already said Required — both languages The DataAnnotations bridge, and the fence it replaces. What it carries, why the reading happens at build time (reflection is the one thing the transpiler cannot take into a browser), that the generated form and a hand-written one are the SAME object — a model adopts it without the page changing and a form outgrows it without a rewrite — and the three diagnostics that say out loud what it cannot take.
📝 docs: forms, in both languages The model, the two pairs of flags that make a form considerate (Touched vs Dirty, Error vs VisibleError), the rule set and why everything but Required passes on empty, conditional validation both ways round (a rule that comes and goes, a field nobody is asking), the surface, and the server's verdict coming back onto the field it belongs to. Fences named: no DataAnnotations bridge yet, and messages are strings because the resx belongs to the app.