|
Welcome the channel on the development of Cro, a set of libraries for building reactive distributed systems, lovingly crafted to take advantage of all the Raku Programming Language has to offer (cro.services). This channel is being logged for historical purposes. Set by lizmat on 24 May 2021. |
|||
|
03:07
Xliff_ left
04:58
Xliff_ joined
11:34
Altai-man joined
11:36
Xliff_ left
18:15
Altai-man left
|
|||
| Xliff | \o | 19:40 | |
| jnthnwrthngtn: Nice job on the new Cro features. | |||
| Are things like resource-from and templates-from-resources lexical? | |||
| Ala 'route { { resources-from %?RESOURCES; templates-from-resources; get -> { template 'templates/index.crotmp' }; }; { template-location 'templates1'; get -> 'from', 'the', 'filesystem' { template 'mytpage.crotmp' }; }; }' | 19:43 | ||
| (hope I got the blocks right...) | |||
|
20:20
patrickb joined
20:33
japhb left
|
|||
| jnthnwrthngtn | Xliff: Not lexical, but scoped to the enclosing `route` block | 22:06 | |
| But you can always use `include route { ... }` to get yourself an inner route scope and use it immediately | |||
| Xliff | So my above example would work with an inner route block enclosing that first get? | 22:19 | |
|
22:46
patrickb left
|
|||
| jnthnwrthngtn | Should do, yes; getting template location and resource scoping right is why the router plugin mechanism was created. | 23:20 | |
|
23:48
xinming left
|
|||