Mathieu Lamiot
Mathieu Lamiot
Pending next alpha to test & compare with the manual process.
Moving back to in-progress to assess @hanna-meda 's findings https://wp-media.slack.com/archives/CUT7FLHF1/p1709125646503859
Hi @mostafa-hisham, I would suggest to take into account [Gustav's proposal ](https://github.com/wp-media/nodejs-treeshaker/issues/367#issuecomment-1586718092) not to use custom HTTP error codes: Even if it does the job for the feature, it can...
Moving issue to "Blocked" while we figure out a solution.
discussion on-going [here](https://wp-media.slack.com/archives/CUT7FLHF1/p1689749482559589)
Following Slack discussion, moving back to "To Grooming" as needs and spec. evolved. Here are the - Must provide an error categorization system to ease operations on failed tasks for...
The solution proposed by @mostafa-hisham is a first step so that we can later on implement error categorization. I created [this task](https://github.com/wp-media/wp-rocket/issues/6072) as a follow-up/placeholder to actually implement the error...
@piotrbak Following @vmanthos feedbacks, it looks like we need to sort out more precisely the use-cases. Without this, we'll be iterating blindly. I am not sure who is more relevant...
Hello @CrochetFeve0251, @vmanthos, @piotrbak, @DahmaniAdame 👋 This PR has been going on for too long now and maybe it is just me, but I am unable to understand its scope...
Thanks @piotrbak 🙏 This message is indeed pretty clear but probably lost (at least for me) in all the discussions. We can block it if there is nothing usable quickly...