refactor: Switch to object pattern for buildTasks - #486
Conversation
ENG-606 Switch to object pattern for buildTasks
Right now buildTasks takes in array of tasks. However, to enable better testing and ensure naming does not conflict we should switch to an object pattern for the return type of buildTasks. We can also deprecate name on task |
🦋 Changeset detectedLatest commit: 3dc8863 The changes in this PR will be included in the next version bump. This PR includes changesets to release 12 packages
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 |
|
Important Review skippedMore than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review. 43 files out of 150 files are above the max files limit of 100. You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
No description provided.