📝 docs: a call through a contract a [ServerOnly] method fulfils is refused (EN, pt-BR, es, fr, de)
Diagnostics, Compiler, SupportedFeatures, BuildFlow and ServerIntegration say
that EQ2010 also refuses a call, or a method group, that reaches a
[ServerOnly] method through the interface member it implements or the method
it overrides, wherever its receiver can be the type that keeps it, across the
app and the projects it references: the twin leaves the method out. A call
bound to a method that is not [ServerOnly], a call through base, a call on a
type that cannot hold the method and a contract no client code calls, as
IServerPrefetch's PrefetchAsync, build (#816). Each page changes in every
language it is written in.
📝 docs: a page's boundary reads only what crosses (EN, pt-BR, es, fr, de)
Diagnostics, Compiler, SupportedFeatures, BuildFlow and ServerIntegration
say which code is client code: every member of a component its module
holds, stateless or stateful, and every class a page reaches. A Server
Action's body and a [ServerOnly] member are never read as client code,
and a [ServerOnly] method leaves every twin. A server API is told once
where the compiler writes it, by its namespace, never also as EQ2004, and
a class that reads a file is EQ2112. EQ2010 refuses a type of the app the
build writes no module for wherever client code names it, a top-level one
included, and the positions the module writes as nothing are free
(#816, #823). Each page changes in every language it is written in.
📝 docs: the build flow page reads in Spanish, French and German
The ASCII diagram keeps its frames: the labels are translated and the padding
recomputed, since a label a few characters longer than its box pushes the border
out and the figure stops being a figure.
Also repoints the anchors that other pages aim into this one. They were written
with the English slugs while the translated pages did not exist, so they resolved
to a page and then to nothing: PackageArchitecture and SupportedFeatures in all
three languages.