Goal: Define the sockets-related functionalities to send and receive data on real-time of Editor component
The information to be sent as data from the application is the main editor code, the current tests in the tests editor and the output. Based on that assumption, these could be possible events:
main_editor_change
tests_editor_change
output_change
The sockets behavior depend on the user role (candidate, evaluator or observer). Each user role has it's own way to send or receive events.
The candidate role is the only one that can send all the data mentioned from the application.
The observer and evaluator roles can receive the events from the backend socket and display them. The output will show the internal tests from the backend in the application and the observer will see the same the candidate sees.
Having in account that the application uses redux and these features requirements, this article seems to be a good starting point.
Goal: Define the sockets-related functionalities to send and receive data on real-time of Editor component
The information to be sent as data from the application is the main editor code, the current tests in the tests editor and the output. Based on that assumption, these could be possible events:
The sockets behavior depend on the user role (candidate, evaluator or observer). Each user role has it's own way to send or receive events.
The candidate role is the only one that can send all the data mentioned from the application. The observer and evaluator roles can receive the events from the backend socket and display them. The output will show the internal tests from the backend in the application and the observer will see the same the candidate sees.
Having in account that the application uses redux and these features requirements, this article seems to be a good starting point.