frontend: add End-to-End Encryption (E2EE) - Updated meeting lobby and room wizard components to handle E2EE settings. - Added E2EE configuration options in the room wizard and lobby services. - Implemented validation for E2EE key input in participant forms. - Enhanced UI to reflect E2EE restrictions on recording and streaming. - Added animations for E2EE warning and info sections. backend: Added E2EE configuration and middleware backend: Added e2ee configuration property to openapi Enables E2EE functionality Configures the application to support end-to-end encryption (E2EE). Copies the necessary worker script to the assets folder. Passes the E2EE key to the meeting component. Adds a script to remove node_modules and dist folder. frontend: Add E2EE UI tests and configuration options webcomponent: Ensure cleanup of test environment after moderation tests frontend: Update E2EE description and restrictions webcomponent: Enhance E2EE UI tests by adding participant interactions and verifying visibility with correct keys backend: Updated start recording example response
SharedMeetComponents
This library was generated with Angular CLI version 18.2.0.
Code scaffolding
Run ng generate component component-name --project shared-meet-components to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project shared-meet-components.
Note: Don't forget to add
--project shared-meet-componentsor else it will be added to the default project in yourangular.jsonfile.
Build
Run ng build shared-meet-components to build the project. The build artifacts will be stored in the dist/ directory.
Publishing
After building your library with ng build shared-meet-components, go to the dist folder cd dist/shared-meet-components and run npm publish.
Running unit tests
Run ng test shared-meet-components to execute the unit tests via Karma.
Further help
To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.