···

       
133
       
 
       
- ✅ **Create unique event types** : Key events should be easily identifiable and have a unique

     

       
134
       
 
       
  names.

     

       
135
       
 
       
- ❌ **Don't listen to debug events inside your exchange**: While it's possible to call

     

       
136
       
-
       
  `client.subscsubscribeToDebugTarget` in an exchange it's only valuable when creating a debugging

     

       
137
       
 
       
  exchange, like the `devtoolsExchange`.

     

       
138
       
 
       
- ❌ **Don't send warnings in debug events**: Informing your user about warnings isn't effective

     

       
139
       
 
       
  when the event isn't seen. You should still rely on `console.warn` so all users see your important

     

···

       
133
       
 
       
- ✅ **Create unique event types** : Key events should be easily identifiable and have a unique

     

       
134
       
 
       
  names.

     

       
135
       
 
       
- ❌ **Don't listen to debug events inside your exchange**: While it's possible to call

     

       
136
       
+
       
  `client.subscribeToDebugTarget` in an exchange it's only valuable when creating a debugging

     

       
137
       
 
       
  exchange, like the `devtoolsExchange`.

     

       
138
       
 
       
- ❌ **Don't send warnings in debug events**: Informing your user about warnings isn't effective

     

       
139
       
 
       
  when the event isn't seen. You should still rely on `console.warn` so all users see your important