Skip to content

Draft: Update socket.io to latest version

Jano requested to merge Feature/PT-UpdateSocketIO into master

What does this MR do?

This MR updates the socket.io library from version 2.3 to 4.4 in on the client and on the server.

How confident are you it won't break things if deployed?

Seems to work fine in the development environment. Users using the old version might need to reload

How to test

Send a private message to any user. You don't even need to log in as the other user; the fact that the message you wrote immediately appears in your own message list proves that the WebSocket works, as this is implemented with a roundtrip to the server.

Automatic tests run fine; no new ones were needed as we don't add any features.

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • set a "for:" label to indicate who will be affected by this change
  • used "state:" labels to track this MR's state until it was beta tested
  • added an entry to CHANGELOG.md
  • added a short text that can be used in the release notes
  • Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
    • Consider writing a detailed description in German.
    • Describe in a few sentences, what should be tested from a user perspective.
    • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
    • Be aware, that also non technical people should understand.
Edited by Thomas Hauschild

Merge request reports