Conversation
🦋 Changeset detectedLatest commit: c695c51 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Claude finished @vicb's task —— View job Changeset ReviewTasks
✅ All changesets look good The changeset for
|
create-cloudflare
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
05de6f8 to
11419d3
Compare
| @@ -1,3 +1,4 @@ | |||
| // eslint-disable-next-line workers-sdk/no-vitest-import-expect | |||
There was a problem hiding this comment.
why this exception? can you add a comment explaining it?
There was a problem hiding this comment.
This is explained in more details in the linked #12346
The idea is to submit multiple larger but PRs convetring the simple/mechanical changes and keep the few changes that will need a more carful review for later - for now ignoring the rule for them.
There was a problem hiding this comment.
thanks 🙂, I'm happy with multiple PRs, but again potentially I'd add a TODO code comment linking to #12346 so that we don't forget to enable the rule elsewhere, but I'll leave this up to you 👍
| R2_PLUGIN_NAME, | ||
| ReplaceWorkersTypes, | ||
| } from "miniflare"; | ||
| // eslint-disable-next-line workers-sdk/no-vitest-import-expect |
There was a problem hiding this comment.
why this exception? can you add a comment explaining it?
Hey Dario, I didn't comment on exceptions because they are temp and will be removed soon (~days) as described in the linked issue #12346. This is only a way to keep reviews reasonably sized and not too time consuming. Does that sound good? |
Sounds good 🙂 (and you know that I really appreciate smaller / reviewable PRs 🙏 ) From my point of view a string replacement from: to seems helpful and it doesn't seem very time consuming, but if you feel that it might be, or if you really find it very unnecessary/problematic, no problem, I'm ok with the code as is 🙂 (PS: I personally feel that todos are valuable even for very temporary changes, since you never know, something unexpected can come up and you might not be able to update the code as quickly as intended, in that case TODOs would still be there as a helpful reminder) |
Part of #12346 - focus is on the miniflare package here
The code of this PR was authored by OpenCode/Opus
A picture of a cute animal (not mandatory, but encouraged)