Feat/socketConnections #113
                
     Draft
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
@doncesarts I found the issue with the disconnections, it seems it is down to the client actually disconnecting/connecting by creating a new ClientSocketEvents every time the useEffect inside the useSocket is used. I think useEffect gets called every time reacts render things right? and if that creates a ClientSocketEvent which in times does this:
const socket = io(ioUri);
I think thats the reason we are getting disconnections, connections.
scrum/packages/scrum-client/src/hooks/useSocket.js
Line 17 in 4250c56
Now i wonder whats the best way to avoid that in the react world. Not that familiar with customHooks or useEffect. I was trying to move the creation outside that but does not seem to work. Any ideas are welcome
DONT merge it pls. This is just to show you the issue