Masafumi Koba

@thomasrockhu-codecov Thanks for your reply. Uploading is now successful! 🎉 Here's the log: ⬇️ ``` ==> Fork detected, tokenless uploading used ``` https://github.com/stylelint/stylelint/actions/runs/9688239908/job/26734397467?pr=7804#step:7:10 ``` ==> Running version v0.7.1 ``` https://github.com/stylelint/stylelint/actions/runs/9688239908/job/26734397467?pr=7804#step:7:33...

@romainmenke Thank you so much for arranging the issues! In my honest opinion, we should focus on #2643 refactoring first. In the refactoring, we can leave that `fix()` doesn't return...

@romainmenke I agree. We should not publish `fix()` yet. This `fix()` signature may change since we're still discussing it. > Can we keep this as an internal feature for now?...

Based on `EditInfo` decided in #7788, I prefer the option `3`. For example: ```ts type EditInfo = { replacement: string; range: Range; }; type Problem = { fix?: (applyFixes: boolean)...

I'm looking at POC PR #7786, but I still cannot understand the importance of the `applyFixes: boolean` argument. If `applyFixes` is `false`, do we need to call `fix()`? If plugin...

Sorry for my late response. I have been considering what a better API is. To maximize usability for plugin authors, I still want to stick to an ESLint-like API. Please...

But in your proposal, plugin authors would have to specify `replacement` in addition to `parsedValue.toString()`, right?

This is a test PR: https://github.com/stylelint/stylelint/pull/7783 Unfortunately, `codecov-action` doesn't seem to have resolved the issue yet. 😢

codecov-action is now back to normal. ✅ See https://github.com/stylelint/stylelint/actions/runs/9688239908/job/26734397467?pr=7804#step:7:55

@Mouvedia Thanks for the report. I'd like to wait and see how the experimental spec goes for a while. Even if these functions are added to `css-functions-list`, they will not...