Thanks for taking a look at this!

Hi @Formasit-chijoh, thanks for taking a look here. This task is more of one of the objectives of the project than a microtask which is why I removed it (I added it by mistake). The patch from earlier was probably abandoned because it was not being actively worked on anymore. I can work on adding more microtasks, however, and meanwhile feel free to take a look at the existing microtask.

I believe the KLawal-WMF account is disabled, so he might not be notified anymore.

I have a basic working version, but that threw up a question: what happens when the separate input field (via separateInput set to true) is enabled? How/where should the icon(s) be displayed in that case?

@Samwilson are we also looking at updating the Extension:Wikisource page with the config variable details?

Thank you for tagging this task with good first task for Wikimedia newcomers!

Added subtasks for the project at T359703.

I was reading some documentation and it seems that chunks of <code></code> should not be wrapped with tvars. Am I missing something?

Hi @Vicolas11, there were two other tasks as well, related to Wikimedia OCR, as you can see above. They have been closed since their patches have been merged.

These screenshots look like you are on the right path. Did you try clicking on the Edit button on the Page namespace and see if you are getting the OCR widget on the editing interface? You might also need the WikiEditor extension for the toolbar to take effect.

@SyedBarimanJan
Feel free to still make a PR if you think you can fix it better. Or take a look at the other microtasks listed in T387267.

Go ahead!

Removing you for now @Frostly

Left feedback on the PR @Harsv567, unassigning you for now

@AshmitaBathre204 removing you from this task for now

Thanks!
I've fixed all the linting errors now but when I try to commit these changes, it gives me a warning that goes:

Ping @Jdlrobson

Hi, I've updated the package version. Then, I ran the lint tests to ensure it is compliant, but it threw some errors. Should I fix them as part of this task or will that be a separate task altogether?

Done :)

Sure, I can do that.

Oh yeah, I have something similar too, but that should help :)

Got it. For some reason, it shows on the prod site but not on my local, but I'll figure that out.
Thanks for the details! I'll take a look and put in a patch soon.

Tried reproducing on my local system (Minerva theme and mobile screen with dark mode) and there seems to be no issue right now. I might be wrong about this, though, so is there a specific sequence of steps I need to try? @Tufor

Hi @Jdlrobson, I can take this up, if it's still relevant!

Ah! I had figured out the part where the parameters get lost but did not think of how the ... operator was used. It makes much more sense now. Thanks for the detailed explanation!

@matmarex the earlier messages from the failing CI have been resolved, but I'm stuck with something else now. I could use some help here :(

I'll try fixing those up, thanks

That's right, I have been trying to replicate the error(s) locally, but haven't been successful so far. It may/may not be related to the fact that I did not change the makeMessage invocation in /tests/phpunit/structure/ApiStructureTest.php (ref) yet. Definitely would be helpful if you can provide some insight on this.

@matmarex I know how to handle the replacing usages part, but I'm not totally sure how the deprecation thing works. Does it just involve marking it as deprecated in the function documentation/description?

Thanks for the review @matmarex, I have changed my patch with tokens that match the initial colours better.

Hi @Jdlrobson, I just put in a patch for this. However, do you think the rest of the CSS (apart from the colours) needs to use the codex tokens too (like border width, perhaps)? Maybe that is for a different task? :)

This seems to be fixed after the PRs were merged to the gitlab repo and have been deployed in the latest version

Done, and deployed a new version of the tool

Hi @Jdlrobson, I agree with you completely. We'll get down to work on this as a top priority and get it closed in the next few days. Hope that works for you!

Thank you for tagging this task with good first task for Wikimedia newcomers!

Adding more context to this task

Adding more context for this task

GitHub PR

Hi @Jdlrobson, I can work on this if it is still relevant :)

In T364642#9833044, @Reputation22 wrote:

not really sure why we have a 3rd repository in picture now

From my testing, it looks like the stacktrace points to Edition::fetchParseData() being the culprit for the above message (although getWikidataItemNumber() could use a try catch as well)