mirror of
https://github.com/redhat-developer/odo.git
synced 2025-10-19 03:06:19 +03:00
8c9bcdeb1f
* Add '/notifications' endpoint for subscribing to server-sent events * Generate server and client * Try implementing the notification service endpoint * Revert "Try implementing the notification service endpoint" This does not seem to work because the generated server always responds with application/json, and it is not possible to respond with a different content-type. This reverts commit cf3ce83677649763b8166c4847501c37246dd757. * Revert "Generate server and client" This reverts commit b985c007a0561edbe185adc3b9582e12aa3f072b. * Revert "Add '/notifications' endpoint for subscribing to server-sent events" This reverts commit c5c903329f13dbe4ec096d83b1c8624fd622bef3. * Implement 'GET /notifications' SSE endpoint and logic to detect and notify Devfile changes * Leverage EventSource to subscribe to Server Sent Events Here, this is being used to automatically reload the Devfile in the YAML view whenever the API server notifies of filesystem changes in the Devfile (and related resources). * Add Preference Client to apiserver CLI This is needed to be able to persist Devfiles from the UI to the filesystem * Add E2E test case * fixup! Leverage EventSource to subscribe to Server Sent Events Co-authored-by: Philippe Martin <phmartin@redhat.com> * Limit the round-trips by sending the whole Devfile content in the DevfileUpdated event data Co-authored-by: Philippe Martin <phmartin@redhat.com> * [Cypress] Make sure to wait for APi responses after visiting the home page Co-authored-by: Philippe Martin <phmartin@redhat.com> * Generate static UI * fixup! [Cypress] Make sure to wait for APi responses after visiting the home page --------- Co-authored-by: Philippe Martin <phmartin@redhat.com>