chore: update dependency eslint-config-kodefox to v0.2.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-kodefox	^0.2.2 -> ^0.3.0
eslint-config-kodefox	0.1.0 -> 0.3.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

PR has been edited

👷 This PR has received other commits, so Renovate will stop updating it to avoid conflicts or other problems. If you wish to abandon your changes and have Renovate start over you may click the "rebase" checkbox in the PR body/description.

If you think this comment is in error and the branch is not modified, try deleting this comment. If it comes back again the next time Renovate runs, please submit an issue or seek config help.

[darcien]

I wonder if the import rule is an overkill if we also specify the order of parent and current dir imports, maybe we just care about the order of the import from packages and from our files.

Especially when this is a lint rule, prettier formatting wont fix it when saving. (We could run eslint --fix, but it's one extra step)

/cc @kodefox/infra

[oshimayoan]

Actually, I don't mind about that as it could force us for better readability. But instead of grouping based on the path parenthesis, I wish it would group the import based on external (all), internal component, internal helper, and internal hooks.

I'll take a look at the library and see if I could change the grouping preference.

/cc @kodefox/infra

[oshimayoan]

Here is how my proposal looks like #400.

[oshimayoan]

Hey @darcien, shall we land this one?

[darcien]

Hey @darcien, shall we land this one?

Should we try to land #400 first?

[oshimayoan]

Good idea! I'll try to update that one first.

[oshimayoan]

As #400 is rejected, shall we land this @darcien?

[darcien]

As #400 is rejected, shall we land this @darcien?

Hmm, maybe we should disable module order rule first.

[oshimayoan]

Hmm, maybe we should disable module order rule first.

I think our conclusion from #400 is to skip the "additional strictness" from that PR, not from what we have on 0.2.x.

So I'm sure we could land this one.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.