|
Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/ Set by moderator on 22 November 2017. |
|||
|
00:19
stmuk_ joined
|
|||
| Geth | cro: timo++ created pull request #47: cro web: allow F5 to work even after navigating |
01:30 | |
|
02:14
stmuk joined
02:57
ilbot3 joined
|
|||
| moderator | Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/ | ||
|
09:09
sena_kun joined
15:07
lizmat joined
|
|||
| Geth | cro-http: 5a65690ade | (Jonathan Worthington)++ | t/http-middleware.t Arrange tests into subtest blocks In preparation for adding further middleware-related tests. |
15:10 | |
| cro-http: ca9d969c8c | (Jonathan Worthington)++ | 2 files Add Cro::HTTP::Middleware::[Request/Response] These roles reduce the boilerplate a bit when writing simple HTTP request and response middleware. |
15:31 | ||
| cro-http: 339923079d | (Jonathan Worthington)++ | lib/Cro/HTTP/Middleware.pm6 Validate request/response middleware behavior |
15:55 | ||
| timotimo | jnthn: should i also drop the "Str" in front of $app-route, not just the where clause? | 15:56 | |
| jnthn | timotimo: Str is treated the same as Any by the route compiler, so it makes no difference | 15:57 | |
| timotimo | then i'll drop it | ||
| pushed it | 16:00 | ||
| is there a specific reason why the websocket-bearing routes have "-road" in their names? | 16:01 | ||
| sena_kun | just a naming convention I thought to be easier for understanding. | 16:05 | |
| and it's only for cro web internals, users can use whatever they want. | |||
| timotimo | right | ||
| but did you invent it or did you find it somewhere else? | 16:06 | ||
| sena_kun | eeeh. I doubt I am the only one, but I "invent" it. | ||
| timotimo | my current app calls them "blah-status-messages", which i don't like very much | ||
| sena_kun | I just thought that "overview" or "stub" is kind of meh, but "overview road" is like "the road where messages related to overview are going". | 16:07 | |
| jnthn | Could just go with -ws (for "web socket"... :) | 16:10 | |
| sena_kun | for sure. :) | 16:12 | |
| Geth | cro: 0f5d6ad26f | (Jonathan Worthington)++ | docs/reference/cro-http-middleware.md Slight re-design of early-response middleware It turns out to be far easier to just `emit` responses, rather than have a special method for that. That's less to learn, perhaps more predictable, and also has a far more natural implementation. |
||
| jnthn | Tried to work out how I'd implemnet method respond in the original proposal and realized it was close to impossible to do it robustly :) | 16:13 | |
| *implement | |||
| sena_kun | Phew. :) | 16:14 | |
| jnthn wonders what the fireworks he can hear (but sadly not sea) are in aid of... | 16:23 | ||
| sena_kun | do we allow `'` character in module names? | 16:41 | |
| timotimo | oh, i wonder if we should get evalable6 in here | 16:43 | |
| jnthn | > class Isn'tThatFunny { } | ||
| (Isn'tThatFunny) | |||
| :) | |||
| sena_kun | :> | 16:44 | |
| jnthn | Wow, I think I got it to work :) | 17:06 | |
| Geth | cro-http: eef63c8edc | (Jonathan Worthington)++ | 3 files Implement Cro::HTTP::Middleware::Conditional Also, provide support for using it at Cro::HTTP::Server level; use at `route`-block level is still to do. |
17:07 | |
| cro/master: 4 commits pushed by timo++, (Timo Paulssen)++, (Jonathan Worthington)++ | 17:13 | ||
|
18:29
lizmat joined
21:18
lizmat joined
|
|||