@rimori/playwright-testing 0.3.20 → 0.3.21-next.1

package/dist/core/RimoriTestEnvironment.d.ts

@@ -220,10 +220,13 @@ export declare class RimoriTestEnvironment {
         triggerOnSidePanelAction: (payload: SidebarAction) => Promise<void>;
         /**
          * Triggers a main panel action event as the parent application would.
-         * This simulates how rimori-main's MainPluginHandler uses EventBus.respond to respond
-         * to plugin's 'action.requestMain' events. When the plugin calls onMainPanelAction(),
-         * it emits '{pluginId}.action.requestMain' and listens for the response.
-         * This method sets up a responder that automatically responds when the plugin emits this event.
+         * This simulates how rimori-main sends the MainPanelAction back to the plugin after
+         * the plugin calls onMainPanelAction() and emits '{pluginId}.action.requestMain'.
+         *
+         * We listen for that outbound emit and respond by injecting a fresh event with
+         * sender='rimori-main'. This avoids the EventBus per-listener blacklist that would
+         * block a {type:'response'} message carrying the same eventId as the original emit.
+         *
          * @param payload - The main panel action payload containing plugin_id, action_key, and action parameters
          */
         triggerOnMainPanelAction: (payload: MainPanelAction) => Promise<void>;

package/dist/core/RimoriTestEnvironment.js

@@ -175,25 +175,27 @@ class RimoriTestEnvironment {
             },
             /**
              * Triggers a main panel action event as the parent application would.
-             * This simulates how rimori-main's MainPluginHandler uses EventBus.respond to respond
-             * to plugin's 'action.requestMain' events. When the plugin calls onMainPanelAction(),
-             * it emits '{pluginId}.action.requestMain' and listens for the response.
-             * This method sets up a responder that automatically responds when the plugin emits this event.
+             * This simulates how rimori-main sends the MainPanelAction back to the plugin after
+             * the plugin calls onMainPanelAction() and emits '{pluginId}.action.requestMain'.
+             *
+             * We listen for that outbound emit and respond by injecting a fresh event with
+             * sender='rimori-main'. This avoids the EventBus per-listener blacklist that would
+             * block a {type:'response'} message carrying the same eventId as the original emit.
+             *
              * @param payload - The main panel action payload containing plugin_id, action_key, and action parameters
              */
             triggerOnMainPanelAction: async (payload) => {
                 if (!this.messageChannelSimulator) {
                     throw new Error('MessageChannelSimulator not initialized. Call setup() first.');
                 }
-                // Listen for when the plugin emits 'action.requestMain' (which becomes '{pluginId}.action.requestMain')
-                // and respond with the MainPanelAction payload, matching rimori-main's EventBus.respond behavior
                 const topic = `${this.pluginId}.action.requestMain`;
-                // Store the payload in a closure so we can respond with it
                 const actionPayload = payload;
-                // Register a persistent auto-responder (not respondOnce) because the plugin may
-                // emit this event multiple times during its lifecycle. Using respondOnce would
-                // only respond to the first request and ignore subsequent ones.
-                this.messageChannelSimulator.respond(topic, actionPayload);
+                // When the plugin emits action.requestMain, immediately emit back the action data
+                // as a fresh event from 'rimori-main' (different sender bypasses the EventBus blacklist).
+                const off = this.messageChannelSimulator.on(topic, async () => {
+                    await this.messageChannelSimulator.emit(topic, actionPayload, 'rimori-main');
+                    off();
+                });
             },
         };
         this.ai = {
@@ -680,12 +682,11 @@ class RimoriTestEnvironment {
             pluginId: options.pluginId,
             guild: {
                 id: 'guild-test-id',
-                // @ts-ignore
                 name: 'Test Guild',
                 city: 'Test City',
                 country: 'Testland',
                 description: 'A dummy guild used for testing purposes.',
-                // @ts-ignore
+                // @ts-expect-error - createdAt field not in type but required for test data
                 createdAt: '2024-01-01T00:00:00.000Z',
                 updatedAt: '2024-01-02T00:00:00.000Z',
                 inviteCode: 'INVITE123',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rimori/playwright-testing",
-  "version": "0.3.20",
+  "version": "0.3.21-next.1",
   "description": "Playwright testing utilities for Rimori plugins and workers",
   "license": "Apache-2.0",
   "repository": {
@@ -26,11 +26,11 @@
   },
   "peerDependencies": {
     "@playwright/test": "^1.40.0",
-    "@rimori/client": "^2.5.29"
+    "@rimori/client": "2.5.32-next.2"
   },
   "devDependencies": {
     "@playwright/test": "^1.40.0",
-    "@rimori/client": "^2.5.29",
+    "@rimori/client": "2.5.32-next.2",
     "@types/node": "^20.12.7",
     "rimraf": "^5.0.7",
     "typescript": "^5.7.2"