New Components - miro_custom_app #17385
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Skipped Deployments
|
WalkthroughThis update introduces new actions and source components for Miro card items, including creating and updating card items, and event sources for card creation and updates. It also adds supporting API methods and property definitions in the app module. Several existing actions and sources have version bumps, and some internal refactoring is performed for shared base logic. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Action (Create/Update Card Item)
participant Miro App
participant Miro API
User->>Action (Create/Update Card Item): Provide card details
Action (Create/Update Card Item)->>Miro App: Call createCardItem/updateCardItem
Miro App->>Miro API: POST/PATCH /boards/{boardId}/cards/{itemId}
Miro API-->>Miro App: Card item response
Miro App-->>Action (Create/Update Card Item): Return response
Action (Create/Update Card Item)-->>User: Show result
sequenceDiagram
participant Source (New/Updated Card Item)
participant Miro App
participant Miro API
participant User
Source (New/Updated Card Item)->>Miro App: Fetch card items (pagination)
Miro App->>Miro API: GET /boards/{boardId}/items?type=card
Miro API-->>Miro App: Return card items
Miro App-->>Source (New/Updated Card Item): Card item data
Source (New/Updated Card Item)->>User: Emit event for new/updated card
Assessment against linked issues
Suggested reviewers
Poem
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
components/miro_custom_app/actions/create-board/create-board.mjsOops! Something went wrong! :( ESLint: 8.57.1 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs components/miro_custom_app/actions/create-card-item/create-card-item.mjsOops! Something went wrong! :( ESLint: 8.57.1 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs components/miro_custom_app/actions/delete-board/delete-board.mjsOops! Something went wrong! :( ESLint: 8.57.1 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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 (
|
michelle0927
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
🧹 Nitpick comments (3)
components/miro_custom_app/actions/delete-item/delete-item.mjs (1)
24-38: Consider surfacing the API response and add minimal error handling
deleteItemmay return useful metadata (HTTP status, deleted item object, etc.). Returning onlyitemIdlimits downstream steps’ visibility.
Also, any 4xx/5xx from the API will currently bubble up without context. A lightweight guard improves DX.- await this.app.deleteItem({ - step, - boardId, - itemId, - }); - - step.export("$summary", "Successfully deleted item"); - - return itemId; + const res = await this.app.deleteItem({ + step, + boardId, + itemId, + }); + + step.export( + "$summary", + `Successfully deleted item ${itemId} (HTTP ${res?.status || 200})`, + ); + + // Return the full response for downstream use + return res?.data ?? { itemId };components/miro_custom_app/actions/delete-board/delete-board.mjs (1)
11-16: Minor tidy-up: reuse the destructuredboardIdYou already destructure
boardIdfromthis, but then call the API withthis.boardId. Using the local variable avoids an unnecessary property access and keeps the code a bit cleaner.- await this.app.deleteBoard({ - step, - boardId: this.boardId, - }); + await this.app.deleteBoard({ + step, + boardId, + });components/miro_custom_app/sources/card-item-updated/test-event.mjs (1)
1-30: Consider differentiating the update test event.The test event structure is identical to the card creation test event. While this provides consistency, consider making the
modifiedAttimestamp more recent thancreatedAtor using a differentmodifiedByuser to better represent a realistic update scenario.- "modifiedAt": "2025-07-01T17:36:23Z", + "modifiedAt": "2025-07-01T17:40:15Z",
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (22)
components/miro_custom_app/actions/create-board/create-board.mjs(1 hunks)components/miro_custom_app/actions/create-card-item/create-card-item.mjs(1 hunks)components/miro_custom_app/actions/create-shape/create-shape.mjs(1 hunks)components/miro_custom_app/actions/create-sticky-note/create-sticky-note.mjs(1 hunks)components/miro_custom_app/actions/delete-board/delete-board.mjs(1 hunks)components/miro_custom_app/actions/delete-item/delete-item.mjs(1 hunks)components/miro_custom_app/actions/get-board/get-board.mjs(1 hunks)components/miro_custom_app/actions/get-items/get-items.mjs(1 hunks)components/miro_custom_app/actions/get-specific-item/get-specific-item.mjs(1 hunks)components/miro_custom_app/actions/list-boards/list-boards.mjs(1 hunks)components/miro_custom_app/actions/update-board/update-board.mjs(1 hunks)components/miro_custom_app/actions/update-card-item/update-card-item.mjs(1 hunks)components/miro_custom_app/actions/update-shape/update-shape.mjs(1 hunks)components/miro_custom_app/actions/update-sticky-note/update-sticky-note.mjs(1 hunks)components/miro_custom_app/miro_custom_app.app.mjs(5 hunks)components/miro_custom_app/package.json(2 hunks)components/miro_custom_app/sources/card-item-updated/card-item-updated.mjs(1 hunks)components/miro_custom_app/sources/card-item-updated/test-event.mjs(1 hunks)components/miro_custom_app/sources/common/base.mjs(1 hunks)components/miro_custom_app/sources/item-position-changed/item-position-changed.mjs(1 hunks)components/miro_custom_app/sources/new-card-item-created/new-card-item-created.mjs(1 hunks)components/miro_custom_app/sources/new-card-item-created/test-event.mjs(1 hunks)
🧰 Additional context used
🧠 Learnings (17)
components/miro_custom_app/actions/update-board/update-board.mjs (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".
components/miro_custom_app/actions/delete-item/delete-item.mjs (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".
components/miro_custom_app/package.json (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.
components/miro_custom_app/actions/create-board/create-board.mjs (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".
components/miro_custom_app/actions/get-specific-item/get-specific-item.mjs (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".
components/miro_custom_app/actions/create-shape/create-shape.mjs (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".
components/miro_custom_app/actions/create-sticky-note/create-sticky-note.mjs (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".
components/miro_custom_app/actions/update-shape/update-shape.mjs (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".
components/miro_custom_app/sources/item-position-changed/item-position-changed.mjs (2)
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#14265
File: components/the_magic_drip/sources/common.mjs:35-43
Timestamp: 2024-10-10T19:18:27.998Z
Learning: In `components/the_magic_drip/sources/common.mjs`, when processing items in `getAndProcessData`, `savedIds` is intentionally updated with IDs of both emitted and non-emitted items to avoid emitting retroactive events upon first deployment and ensure only new events are emitted as they occur.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#15376
File: components/monday/sources/name-updated/name-updated.mjs:6-6
Timestamp: 2025-01-23T03:55:15.166Z
Learning: Source names in Monday.com components don't need to start with "New" if they emit events for updated items (e.g., "Name Updated", "Column Value Updated") rather than new items. This follows the component guidelines exception where the "New" prefix is only required when emits are limited to new items.
components/miro_custom_app/actions/update-sticky-note/update-sticky-note.mjs (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".
components/miro_custom_app/sources/new-card-item-created/test-event.mjs (3)
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#14265
File: components/the_magic_drip/sources/common.mjs:35-43
Timestamp: 2024-10-10T19:18:27.998Z
Learning: In `components/the_magic_drip/sources/common.mjs`, when processing items in `getAndProcessData`, `savedIds` is intentionally updated with IDs of both emitted and non-emitted items to avoid emitting retroactive events upon first deployment and ensure only new events are emitted as they occur.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12697
File: components/salesforce_rest_api/sources/common-webhook-methods.mjs:1-71
Timestamp: 2024-10-08T15:33:38.240Z
Learning: The `common-webhook-methods.mjs` object is designed to be extended, similar to an abstract class, and intentionally does not implement certain methods like `generateWebhookMeta` and `getEventType` to enforce implementation in subclasses.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12697
File: components/salesforce_rest_api/sources/common-webhook-methods.mjs:1-71
Timestamp: 2024-07-24T02:06:47.016Z
Learning: The `common-webhook-methods.mjs` object is designed to be extended, similar to an abstract class, and intentionally does not implement certain methods like `generateWebhookMeta` and `getEventType` to enforce implementation in subclasses.
components/miro_custom_app/sources/card-item-updated/test-event.mjs (1)
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#14265
File: components/the_magic_drip/sources/common.mjs:35-43
Timestamp: 2024-10-10T19:18:27.998Z
Learning: In `components/the_magic_drip/sources/common.mjs`, when processing items in `getAndProcessData`, `savedIds` is intentionally updated with IDs of both emitted and non-emitted items to avoid emitting retroactive events upon first deployment and ensure only new events are emitted as they occur.
components/miro_custom_app/sources/common/base.mjs (1)
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#14265
File: components/the_magic_drip/sources/common.mjs:35-43
Timestamp: 2024-10-10T19:18:27.998Z
Learning: In `components/the_magic_drip/sources/common.mjs`, when processing items in `getAndProcessData`, `savedIds` is intentionally updated with IDs of both emitted and non-emitted items to avoid emitting retroactive events upon first deployment and ensure only new events are emitted as they occur.
components/miro_custom_app/actions/create-card-item/create-card-item.mjs (3)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-10-08T15:33:38.240Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-07-04T18:11:59.822Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.
components/miro_custom_app/sources/card-item-updated/card-item-updated.mjs (4)
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#14265
File: components/the_magic_drip/sources/common.mjs:35-43
Timestamp: 2024-10-10T19:18:27.998Z
Learning: In `components/the_magic_drip/sources/common.mjs`, when processing items in `getAndProcessData`, `savedIds` is intentionally updated with IDs of both emitted and non-emitted items to avoid emitting retroactive events upon first deployment and ensure only new events are emitted as they occur.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#15376
File: components/monday/sources/name-updated/name-updated.mjs:6-6
Timestamp: 2025-01-23T03:55:15.166Z
Learning: Source names in Monday.com components don't need to start with "New" if they emit events for updated items (e.g., "Name Updated", "Column Value Updated") rather than new items. This follows the component guidelines exception where the "New" prefix is only required when emits are limited to new items.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12697
File: components/salesforce_rest_api/sources/common-webhook-methods.mjs:1-71
Timestamp: 2024-10-08T15:33:38.240Z
Learning: The `common-webhook-methods.mjs` object is designed to be extended, similar to an abstract class, and intentionally does not implement certain methods like `generateWebhookMeta` and `getEventType` to enforce implementation in subclasses.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12697
File: components/salesforce_rest_api/sources/common-webhook-methods.mjs:1-71
Timestamp: 2024-07-24T02:06:47.016Z
Learning: The `common-webhook-methods.mjs` object is designed to be extended, similar to an abstract class, and intentionally does not implement certain methods like `generateWebhookMeta` and `getEventType` to enforce implementation in subclasses.
components/miro_custom_app/sources/new-card-item-created/new-card-item-created.mjs (4)
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#14265
File: components/the_magic_drip/sources/common.mjs:35-43
Timestamp: 2024-10-10T19:18:27.998Z
Learning: In `components/the_magic_drip/sources/common.mjs`, when processing items in `getAndProcessData`, `savedIds` is intentionally updated with IDs of both emitted and non-emitted items to avoid emitting retroactive events upon first deployment and ensure only new events are emitted as they occur.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#15376
File: components/monday/sources/name-updated/name-updated.mjs:6-6
Timestamp: 2025-01-23T03:55:15.166Z
Learning: Source names in Monday.com components don't need to start with "New" if they emit events for updated items (e.g., "Name Updated", "Column Value Updated") rather than new items. This follows the component guidelines exception where the "New" prefix is only required when emits are limited to new items.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12697
File: components/salesforce_rest_api/sources/common-webhook-methods.mjs:1-71
Timestamp: 2024-10-08T15:33:38.240Z
Learning: The `common-webhook-methods.mjs` object is designed to be extended, similar to an abstract class, and intentionally does not implement certain methods like `generateWebhookMeta` and `getEventType` to enforce implementation in subclasses.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12697
File: components/salesforce_rest_api/sources/common-webhook-methods.mjs:1-71
Timestamp: 2024-07-24T02:06:47.016Z
Learning: The `common-webhook-methods.mjs` object is designed to be extended, similar to an abstract class, and intentionally does not implement certain methods like `generateWebhookMeta` and `getEventType` to enforce implementation in subclasses.
components/miro_custom_app/actions/update-card-item/update-card-item.mjs (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Lint Code Base
- GitHub Check: Publish TypeScript components
- GitHub Check: Verify TypeScript components
🔇 Additional comments (21)
components/miro_custom_app/actions/delete-item/delete-item.mjs (1)
7-7: Version bump looks good – double-check ancillary metadataThe patch version increment to
0.0.2is appropriate for a non-functional change.
Please ensure corresponding updates are reflected in the CHANGELOG and any marketplace listing so users can understand what changed.components/miro_custom_app/actions/delete-board/delete-board.mjs (1)
6-6: Version bump looks goodIncrementing the version to
0.0.2cleanly reflects the release cycle and aligns with the other action updates in this PR. No issues spotted here.components/miro_custom_app/sources/common/base.mjs (2)
14-28: LGTM! Well-structured prop definitions.The new
teamIdandboardIdprops follow proper Pipedream patterns withpropDefinitionusage, and the dependency relationship between them is logically sound.
31-36: LGTM! Standard timestamp tracking implementation.The
_getLastTsand_setLastTsmethods provide a clean abstraction for timestamp management in polling sources, following established patterns for event deduplication.components/miro_custom_app/actions/update-shape/update-shape.mjs (1)
8-8: LGTM! Coordinated version bump.The version increment aligns with the broader package update from 0.1.0 to 0.2.0 and appears to be part of a synchronized release.
components/miro_custom_app/actions/get-items/get-items.mjs (1)
7-7: LGTM! Consistent version increment.The version bump is consistent with other action components and aligns with the overall package update strategy.
components/miro_custom_app/package.json (2)
3-3: LGTM! Appropriate version bump.The minor version increment reflects the addition of new functionality (card item actions and sources) while maintaining backward compatibility.
16-16: Verify compatibility of @pipedream/platform v3.1.0 in miro_custom_appA targeted check in
components/miro_custom_appdid not reveal any direct@pipedream/platformimports. Please confirm that the component has been updated to use the new v3 APIs and test it end-to-end:
- Ensure any HTTP requests use
import { axios } from "@pipedream/platform";
instead of custom or older imports- Update uses of platform constants or errors (e.g.
DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,ConfigurationError) if their signatures changed- Run component/unit tests for
miro_custom_appto catch runtime breakagesDiff in
package.json:--- package.json - "@pipedream/platform": "^1.5.1" + "@pipedream/platform": "^3.1.0"components/miro_custom_app/actions/get-board/get-board.mjs (1)
6-6: LGTM! Consistent version management.The version increment maintains consistency across all action components and supports the coordinated release strategy.
components/miro_custom_app/actions/update-board/update-board.mjs (1)
7-7: Patch version increment looks goodThe bump to
0.0.2keeps this action in sync with its peers and follows the repository’s versioning convention. No further issues spotted.components/miro_custom_app/actions/create-board/create-board.mjs (1)
5-5: Version bump acknowledged
0.0.2is consistent with the coordinated update across related actions. ✅components/miro_custom_app/actions/list-boards/list-boards.mjs (1)
7-7: Minor version alignment verified
0.0.3correctly advances this action ahead of the others that were already on0.0.2; no other changes required.components/miro_custom_app/actions/create-shape/create-shape.mjs (1)
7-7: Patch release recordedThe version tag now reads
0.0.2, matching the rest of the component set. All good.components/miro_custom_app/actions/create-sticky-note/create-sticky-note.mjs (1)
8-8: Version updated without functional change
0.0.2applied; no other modifications detected.components/miro_custom_app/actions/get-specific-item/get-specific-item.mjs (1)
7-7: LGTM: Version bump is appropriate.The version increment from "0.0.1" to "0.0.2" aligns with the coordinated maintenance update across multiple Miro custom app actions.
components/miro_custom_app/actions/update-sticky-note/update-sticky-note.mjs (1)
8-8: LGTM: Consistent version increment.The version update from "0.0.1" to "0.0.2" is consistent with the coordinated maintenance update across the Miro custom app actions.
components/miro_custom_app/sources/item-position-changed/item-position-changed.mjs (1)
8-8: LGTM: Version increment with successful refactoring.The version update from "0.0.1" to "0.0.2" is appropriate. The component appears to have been successfully refactored to use the shared base module while maintaining correct position change detection functionality.
components/miro_custom_app/sources/new-card-item-created/test-event.mjs (1)
1-30: LGTM: Comprehensive test event structure.The test event provides a realistic and complete representation of a Miro card item with all expected properties including styling, geometry, positioning, API links, and user metadata. This will serve well as a test fixture for the new card item creation source component.
components/miro_custom_app/sources/card-item-updated/card-item-updated.mjs (1)
6-6: LGTM - Correct naming convention for update events.The source name "Card Item Updated" correctly follows the component guidelines by not using the "New" prefix since this emits events for updated items rather than new items.
components/miro_custom_app/miro_custom_app.app.mjs (2)
143-152: LGTM - Improved fallback handling in itemId options.The enhanced itemId options method with optional chaining and multiple fallback options (
data?.content || data?.title || data?.[type] || type) provides robust label generation for different item types.
243-251: LGTM - New API methods follow consistent patterns.The new API methods
createCardItem,listBoardMembers, andupdateCardItemfollow the established patterns in the codebase and correctly implement the Miro API endpoints.Also applies to: 300-307, 335-343
components/miro_custom_app/actions/create-card-item/create-card-item.mjs
Show resolved
Hide resolved
components/miro_custom_app/sources/new-card-item-created/new-card-item-created.mjs
Show resolved
Hide resolved
components/miro_custom_app/sources/new-card-item-created/new-card-item-created.mjs
Show resolved
Hide resolved
components/miro_custom_app/sources/card-item-updated/card-item-updated.mjs
Show resolved
Hide resolved
components/miro_custom_app/sources/card-item-updated/card-item-updated.mjs
Show resolved
Hide resolved
components/miro_custom_app/actions/update-card-item/update-card-item.mjs
Show resolved
Hide resolved
luancazarine
left a comment
luancazarine
left a comment
There was a problem hiding this comment.
Hi @michelle0927, LGTM! Ready for QA!
Resolves #7195
Summary by CodeRabbit
New Features
Bug Fixes
Chores