Marco Ciampini

Results 134 comments of Marco Ciampini

> I've added #42725 to the list. Hope that's ok! Of course it is, thank you! I must flag that I currently don't really have the capacity to work on...

Thank you @alexstine for your determination in working on an alternative approach! Apologies if I'm not being very responsive, but I've been having a busy week (and I won't be...

@gziolo 's advice makes sense to me — we could do something like ```diff diff --git a/.eslintrc.js b/.eslintrc.js index 22c354394d..e70d083496 100644 --- a/.eslintrc.js +++ b/.eslintrc.js @@ -224,6 +224,13 @@ module.exports...

Hey folks, I'll keep an eye open for updates on this issue but at the moment I'm struggling to keep up with my notifications queue. I'll try to get to...

After reviewing @alexstine 's PR, I also created a PR with an alternative approach #44526 — it would be good if @joedolson and @costdev (who were both able to reproduce...

> Hello everyone 👋 I want to work on this issue. Can anyone tell me if I need to convert all js file to typescript. (example in **DropdownMenu** have `index.js`...

Alright, I've edited this issue's description and added all components/folders in the package. There's still a couple of things of which I’m not sure yet: 1. so far, even with...

> From a "value" perspective I don't think there's a compelling reason to spend contributor time on updating unit tests and storybook examples to use TypeScript. I see your point,...

**Update**: a first version of the TypeScript refactoring guidelines has been added to [the `@wordpress/components` package guidelines](https://github.com/WordPress/gutenberg/blob/trunk/packages/components/CONTRIBUTING.md#refactoring-a-component-to-typescript). From now on, we will be starting to accept help on this task...

Hey all 👋 Is this PR ready to be merged? Since some time has passed, should we rebase it before doing so?