You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks to @jiwon79, and their comment under CoconutGoodie/figma-plugin-react-vite#4, I see a very crucial architectural issue. @common should not include any message handling, as it might depend on a certain side, which might be unavailable on another side.
Monorepo Networker should change its approach, so now handlers are placed under their respective sides.
What actions should be taken?
Message receive handlers are highly side-dependent. Therefore, they should be handled on their corresponding side. As you suggested ✅
@common/network should only be there to;
Define sides - Which sides are available throughout the application ✅
Define communication strategies - Which strategy a certain side uses to communicate with another side ✅
Define which messages are there - Which messages are present for a certain side ✅
The text was updated successfully, but these errors were encountered:
Summary
Thanks to @jiwon79, and their comment under CoconutGoodie/figma-plugin-react-vite#4, I see a very crucial architectural issue.
@common
should not include any message handling, as it might depend on a certain side, which might be unavailable on another side.Monorepo Networker should change its approach, so now handlers are placed under their respective sides.
What actions should be taken?
@common/network
should only be there to;The text was updated successfully, but these errors were encountered: