|
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:28
avuserow joined
|
|||
| japhb | jnthnwrthngtn: github.com/jnthn/p6-log-timeline/pull/11 -- I figured the best examples come in PR form. :-) | 04:40 | |
|
09:22
patrickb joined
|
|||
| jnthnwrthngtn | japhb: Wow! | 09:25 | |
|
09:53
sena_kun left
|
|||
| Altreus | is there a bot here that links me to docs? | 09:59 | |
| eh that should be a #raku question tbh | 10:00 | ||
|
10:00
sena_kun joined
|
|||
| jnthnwrthngtn | japhb: That looks really good, and gives me all I need to figure out how to do it that way on the socket also. Thanks! | 10:03 | |
| Altreus | japhb++ # I don't understand it and jnthn learned from it so it must be good | 10:08 | |
| jnthnwrthngtn | Altreus: Log::Timeline is a way to instrument programs with logging of events (things at a point in time) and tasks (things that happen over time). There's a visualizer in Comma. It's integrated in Cro in various places. At the moment it uses JSON serialization; japhb++ has demonstrated using CBOR instead, which is more compact and hopefully faster. | 10:11 | |
| Altreus | Ah yeah, you suggested Log::Timeline to myself and kawaii_ but I looked at it and went "argh" and I didn't actually make use of it :D | 10:12 | |
| jnthnwrthngtn | Why "argh"? :D | ||
| Altreus | Everything new was argh at the time | 10:13 | |
| It may yet be argh but I don't have a specific reason why | |||
| jnthnwrthngtn | ah, ok :) | ||
| Altreus | Honestly raku is still a bit argh but it's because I'm busy with not-raku | 10:14 | |
| I don't have the brain space for that many contexts :) | |||
| jnthnwrthngtn | Ah, fair enough :) | ||
| Altreus | wish I could fit in some time though; I really want API::Discord to be useful | 10:17 | |
| Geth | cro-webapp/template-parts: 8684a053d7 | (Jonathan Worthington)++ | 7 files Introduce template parts The feature is primarily aimed at allowing for data for common elements of pages to be produced and obtained without needing to explicitly pass it in to every template call (think a header that has an indication of if a user is currently logged in, or about their shopping cart content). A `route` block integration in a subsequent commit will allow for that. ... (8 more lines) |
11:24 | |
|
11:55
sena_kun left,
sena_kun joined
|
|||
| Geth | cro-webapp/master: 4 commits pushed by (Jonathan Worthington)++ | 12:41 | |
| cro-webapp/template-parts: 98f4d0f08f | (Jonathan Worthington)++ | 3 files Test interaction of parts, use, and macros |
12:58 | ||
| cro-webapp/template-parts: 6fe265d1fa | (Jonathan Worthington)++ | 7 files Introduce template parts The feature is primarily aimed at allowing for data for common elements of pages to be produced and obtained without needing to explicitly pass it in to every template call (think a header that has an indication of if a user is currently logged in, or about their shopping cart content). A `route` block integration in a subsequent commit will allow for that. ... (8 more lines) |
13:35 | ||
| cro-webapp/template-parts: ee045d815c | (Jonathan Worthington)++ | 3 files Test interaction of parts, use, and macros |
|||
| jnthnwrthngtn | Sorry for the dupe; rebased it after the templates from resources thing to avoid even more conflicts in what comes next... | ||
| Altreus | bad form to complain about the outcome of someone contributing their free time :) | 13:43 | |
|
14:53
AlexDaniel left
14:54
AlexDaniel joined
14:58
sena_kun left,
sena_kun joined
|
|||
| Geth | cro-webapp/template-parts: 1386911341 | (Jonathan Worthington)++ | 3 files Implement route block template part providers While one can explicitly provide template part data in the `template` call, it will often be more convenient to avoid repetition and write a `template-part` provider in the `route` block. This will be called when the template part is encountered during rendering. It may optionally have a parameter, which will be bound to `request.auth` so long as the type matches; said type matching allows for different providers for logged in or not, or different levels of user, or just to pull data out of a session (for example, shopping cart content). |
15:15 | |
|
15:35
patrickb left
|
|||
| Geth | cro-webapp: jnthn++ created pull request #43: Implement template parts |
16:40 | |
| cro: ee70fb730e | (Jonathan Worthington)++ | docs/reference/cro-http-router.md Document serving content from %?RESOURCES |
17:12 | ||
| cro: 1bee19a626 | (Jonathan Worthington)++ | docs/reference/cro-webapp-template.md Document templates from resources Also update documentation on how `template-location` works, and add a note about `CRO_DEV=1` for live reload. |
17:35 | ||
| japhb | Ah, very happy to see my PR hit the mark. Thanks for merging, jnthnwrthngtn! :-) | 19:15 | |
| japhb watches as Cro::WebApp slowly becomes "Mason, reimagined for the 2020s". :-) | 19:16 | ||
| japhb used Mason for several jobs, and likes Cro::WebApp, so it's making me pretty happy | |||