Closed pjayathissa closed 3 years ago
I agree with you, the best approach is to put back the buzz
module in index.js
. We all tried to fix that issue but we could not solve it so it is better to have the buzz functions inside index.js and avoid issues.
@FedericoTartarini I tried to fix Issues #91 #90 but I kept getting stuck in excessive complexity. The easier option was just to revert the 'buzz' module back to index.js.
This seems to fix the issues for now. And it was only about 80 lines of code that needed moving back, as there was redundancy with the two instances of the
messaging.peersocket
andfiletransfer
functions. This redundancy came about in my previous pull request when I brought the flow selector back.This fix also solved a cyclic importing warning (buzz importing index, and index importing buzz).
I'm testing this on my versa right now. And it seems to be ok