05:54 | <Domenic> | plinss/webidlparser being unmaintained is indeed starting to get quite painful. It'd be great to either maintain it or replace it. E.g. https://github.com/whatwg/webidl/pull/1211 has been blocked for over a month but multiple other specs are starting to build on it. |
09:58 | <annevk> | We might have to bump actions/setup-python to 4 I think. The current one outputs a warning |
09:58 | <annevk> | Per https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ we have until June next year |
14:15 | <annevk> | This might be of interest to some people here: https://github.com/HTTPWorkshop/workshop2022/blob/main/report.md |
14:24 | <annevk> | krosylight: Domenic: I don't think diagrams need to be part of the build. They're generated so rarely it seems kind wasteful. Having a script at hand to make changes easier should suffice in my opinion. |
14:44 | <krosylight> | krosylight: Domenic: I don't think diagrams need to be part of the build. They're generated so rarely it seems kind wasteful. Having a script at hand to make changes easier should suffice in my opinion. |
14:44 | <annevk> | Luca Casonato: does Deno care about https://github.com/whatwg/fetch/pull/1541? |
14:51 | <annevk> | krosylight: that also makes me lean toward excluding package.json , but don't care too strongly. Although, if there's going to be dependency alerts then let's disable that and just review the output diff when needed? |
14:52 | <krosylight> | you mean package-lock? |
14:52 | <annevk> | krosylight: that seems likely. :-) |
14:53 | <krosylight> | I just followed what webidl already does there, let's see what domenic thinks |
14:53 | <annevk> | Well Web IDL is slightly different in that there it's part of the build |
14:53 | <annevk> | But sure, waiting for Domenic makes a lot of sense |
19:27 | <TabAtkins> | Re: widlparser, I'm happy to start taking cracks at maintaining, since I've read into it enough at this point for some refactorings. I'll see what i can do. |