getting closer to full port of web app starter
This commit is contained in:
@@ -4,7 +4,7 @@ COMPONENT(Request& context)
|
||||
:desc
|
||||
Defines the default component entrypoint for the current `.uce` file.
|
||||
|
||||
`component()` and `render_component()` invoke `COMPONENT(Request& context)` by default. Named component entrypoints use `COMPONENT:NAME(Request& context)`.
|
||||
`component()` and `component_render()` invoke `COMPONENT(Request& context)` by default. Named component entrypoints use `COMPONENT:NAME(Request& context)`.
|
||||
|
||||
This keeps page rendering and component rendering separate:
|
||||
|
||||
@@ -16,7 +16,7 @@ A file intended only for component reuse can define `COMPONENT()` without defini
|
||||
|
||||
Inside component handlers, props arrive through `context.call`.
|
||||
|
||||
When you call `component(":NAME", props, context)` or `render_component(":NAME", props, context)`, the runtime resolves `:NAME` against the current `.uce` file instead of requiring the file name again.
|
||||
When you call `component(":NAME", props, context)` or `component_render(":NAME", props, context)`, the runtime resolves `:NAME` against the current `.uce` file instead of requiring the file name again.
|
||||
|
||||
Examples:
|
||||
`COMPONENT(Request& context)`
|
||||
@@ -31,6 +31,6 @@ Examples:
|
||||
|
||||
:see
|
||||
>component
|
||||
>render_component
|
||||
>component_render
|
||||
>1_RENDER
|
||||
>1_WS
|
||||
|
||||
Reference in New Issue
Block a user