- 
                Notifications
    You must be signed in to change notification settings 
- Fork 7.5k
fix: remove adaptV4Theme and migrate to native MUI v5 theme structure #16294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
fix: remove adaptV4Theme and migrate to native MUI v5 theme structure #16294
Conversation
Remove Emoji
| Hi, thanks for your contribution! | 
feat: Add plugin head script inclusion to multiple HTML files fix
| Does this have any practical implications? | 
| 
 Yes — it addresses the deprecation warning from MUI regarding  Practical implications include: 
 | 
| What I mean is: are there any implications such as visual changes because the change in theme structure? | 
| 
 No, there aren't any visual changes introduced by this change. | 
…ctly to close page (#49)
* fix(deploy): handle lib-jitsi-meet submodule * feat(host): use specific remote and local isHost functions * fix(tests): close invite dialog on meeting join
… feature for moderators (#60) * Add howler audio library dependency * Integrate Howler.js for sound management * Refactor sound system to use centralized SoundService * Fix trailing whitespace in SoundService.ts comment * Add Howler.js support * Implement unregister method for proper memory management * Replace sound-related Redux actions (playSound, registerSound, unregisterSound, stopSound) with direct SoundService calls across all middleware and components. * feat(SoundService): add muteSound method to SoundService for individual sound control * Remove unused SoundCollection component * Refactor sound system to centralize playback logic in SoundService * Remove unnecessary base sounds feature module * Replace 'any' with 'unknown' type in SoundService error handlers to fix typescript errors * Refactor sound system to pass state parameter to SoundService.play() and fix redux sound state * Add audio output device switching support to SoundService * Fix Typescript errors * fix lint error * Remove old sound middleware registration logic * Integrate sounds reducer with app state * Add 'optional' property to each sound in features/base/sounds redux store * Add sound muting functionality to base sounds feature * Refactor sound handling in settings components and integrate mute functionality * Update language files * lint lang files Remove unnecessary @types/howler dependency Revert "Remove unnecessary @types/howler dependency" This reverts commit 9e755d9. * Remove unused howler module declaration from globals.d.ts * Revert "Remove unused howler module declaration from globals.d.ts" This reverts commit 9a953e1. * Add global sound muting feature for moderators * add Sounds header in ModeratorTab Update mute sound label to use localized "Mute" text change Sound header to h4 * Refactor sound handling: streamline sound registration and localization * add 'moderation' property to sounds state * feat(sounds): implement sound localization in SoundService * create a single getLocalizedSound func to get both, localized sound and filepath * Refactor SoundService * create setMuteSoundGlobal function to send global sound mute command * fix(sounds): make sound file paths relative * Fix lint * remove unnecessary logs * pass in 'languages' prop when playing recording on and off sounds * fix(transcribing): add conference check before playing recording sound * Remove unneceassry sinkId param when initializing howler * fix lint * Fix lint * fix lint
* add refresh token --------- Co-authored-by: ibrahim ali <[email protected]>
…d full attendance (#94)
Summary
This PR removes the usage of the deprecated
adaptV4Theme()helper and migrates the theme definition to MUI v5's nativecreateThemestructure.Why
MUI logs the following deprecation warning:
While
adaptV4Theme()was useful during the transition from MUI v4 to v5, it is no longer recommended and may be removed in future releases.What Changed
createTheme(adaptV4Theme(...))with direct usage ofcreateTheme(...)adaptV4ThemeimportResult