[06:58:52] @cosmicalpha can we make githubbot also add the 'pull request ready' project automatically when forwarding pr opened message? [06:59:08] Yes I plan to do that. [06:59:18] I just forgot when making it. [15:55:40] @posix_memalign user scripts with JSDoc comments are sometimes misinterpreted as template invocations somehow [15:56:04] https://cdn.discordapp.com/attachments/1006789349498699827/1557058872382849054/Screenshot_2026-10-06_at_11.55.52_AM.png?backend=b2&ex=6ac66b93&is=6ac51a13&hm=06135e2b5420b4f262e07a5568a1d0df271ebbd6a2f3ce2993d7144bc532b6ce& [15:56:28] that's just syntax highlighting [15:56:36] when editing it it also shows up under "pages included on this page" [15:56:46] https://cdn.discordapp.com/attachments/1006789349498699827/1557059048703008949/Screenshot_2026-10-06_at_11.56.43_AM.png?backend=b2&ex=6ac66bbd&is=6ac51a3d&hm=cce2d6b7e2437a6c0cadf9610ea577cdc3a935996a653cd60354132ce55b99ed& [15:57:06] I'm not sure what would happen if that template actually existed [15:57:06] does it affect the whatlinkshere for the template in question [15:57:15] if not then no point worrying about it [15:59:25] it does affect whatlinkshere [15:59:33] just tested it with Template:Colon [16:00:02] at least it doesn't seem to be transcluding it into the actual JS [16:07:22] yeah everything within two curly braces `{{` `}}` is treated like a page link even if not rendered as such. [16:07:49] It also makes scripts with Vue template literals v annoying to handle [16:08:21] you offset it by enclosing everything in `
` or ``
[16:09:03] 	  I doubt MW core is changing this behaviour since it's the same behaviour that lets us place wiki JS/CSS files in categories
[16:22:59] 	  Also the current MW minifier doesn't support optional chaining (`?.`). Your script will work fine when loaded raw but not when it is pre-processed on MediaWiki:Common.js or MediaWiki:Gadget-X.js.
[16:23:17] 	  I am aware
[16:25:22] 	  It's still a point of consideration depending on how many people you're aiming your scripts to be used by
[16:28:57] 	  now that I think of it, I don't think the current minifier supports spread operator either. or maybe I'm misremembering.
[16:29:43] 	  idk, I'm using a script that can be minified with the sole purpose of loading the others raw so I can use the modern syntax features
[16:30:35] 	  my secret is that I'm writing on Typescript always
[16:40:00] 	  I think I've used it before
[16:40:47] 	  yeah spread is es6
[16:42:19] 	  can you believe we're in the great 1.46 and MW still doesn't support optional chaining
[16:42:37] 	  literally downleveling TS to 2019 purely for it
[17:10:10] 	  I replied to a comment on [[Requests for Comment/Reducing Superfluous Steward Supervision]]. After clicking 'reply' the final two proposals on the page got deleted. I noticed this instantly and reverted my edit. I did not even open VisualEditor or SourceEditor; I just clicked on the reply button.
[17:10:11] 	  
[17:16:05] 	  [1/2] Looks fine in wikitext. It's possible that a runaway tag and/or template is hiding a bunch of content though.
[17:16:05] 	  [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1557079008179392532/image.png?backend=b2&ex=6ac67e54&is=6ac52cd4&hm=23b9bb04d62647368aa1338fb3151a3be4e9e0b2133202263959df9fb9b71361&
[17:16:28] 	  perhaps something to do with the  tags?
[17:18:05] 	  also, I dislike the pre-save transform being mandatory, it forced me to do `"~".repeat(x)` to get signatures in templates
[17:26:53] 	  I've seen a few negative things about  tags, but I don't actually understand what's wrong with them - are they known for causing weird errors?
[17:27:43] 	  I don't think they are the culprit. They are properly closed per manual inspection, and if they are not it will be very obvious because everything else on the page would be in plain text.
[17:29:11] 	  It works in extensions though, which has always been really odd to me
[17:29:11] 	  [1/2] There we go
[17:29:12] 	  [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1557082305875681390/image.png?backend=b2&ex=6ac68166&is=6ac52fe6&hm=289f3635589c3649291396083b59b1a5583816b1776644a4b891666c7a25603b&
[17:29:21] 	  I wonder if the minifier does something differently for extensions
[17:30:36] 	  Still not sure why a reply triggers it. Maybe the parser doesn't like seeing tags nested this way.
[17:31:16] 	  [1/2] And a runaway nowiki tag
[17:31:16] 	  [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1557082827919720519/image.png?backend=b2&ex=6ac681e3&is=6ac53063&hm=cc99a198e6023ad3d41bf5ecbdf7b69adf919e1856ec46c47209a2a68aa0f76b&
[17:37:16] 	  [1/2] Turns out the second one is the root cause. The first one is fine even if it is not proper use of HTML.
[17:37:16] 	  [2/2] @uranium_mandy I restored your comment now that the page is fixed.
[17:38:11] 	  Thanks
[17:42:12] 	  https://meta.miraheze.org/wiki/Special:RequestWikiQueue/92678#mw-section-comments create wiki AI output \n instead of an actual newline
[17:42:34] 	  might have something to do with the request language not being english?