There was an error while loading. Please reload this page.
docs: capabilities where there is no context, in both languages Three things preview.33 changed about asking for a capability, and one the page was quietly wrong about. `GetService<T>()` on the component itself, for OnMount and OnUnmount and event handlers: the page said a component at depth resolves through the context, which is true and was the only answer, so a subscription had to live inside Build behind a run once flag. What an absent capability does, as a table, because the C# already says it: a non nullable parameter is the component promising it cannot work without one, and gets an error naming the capability and the component instead of a null that fails later inside code that never mentions capabilities. A nullable one is the author saying they cope. Handing one over in a test, with the scope that puts back what it replaced. And the constructor section now says the rest of its own story: any constructor form declares a dependency the same way (a primary one did not until now), and nobody passes it at the call site or through the generated factory either. Version marks verified against the tags rather than guessed: every symbol here first appears in a commit whose earliest tag is v0.2.0-preview.33.
docs: the clock joins the capability table, in both languages IClock is the capability whose answer is nothing but change, and the page says the whole contract: the OnMount/OnUnmount pair, the server that never ticks (so the first paint is what it was built with), the missed tick that is dropped rather than replayed, and why it is periodic and not a frame clock. Marked since preview.31, which is the release it ships in.
📝 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 interaction contract catches up with the a11y pass — both languages
📝 docs: pt-BR pages link to pt-BR pages
📝 docs: Storage and Capabilities speak pt-BR