Skip to content

Conversation

@Zaid0412
Copy link
Contributor

@Zaid0412 Zaid0412 commented Aug 3, 2025

Summary

This PR removes the usage of the deprecated adaptV4Theme() helper and migrates the theme definition to MUI v5's native createTheme structure.

Why

MUI logs the following deprecation warning:

MUI: adaptV4Theme() is deprecated. Follow the upgrade guide on https://mui.com/r/migration-v4#theme.

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

  • Replaced createTheme(adaptV4Theme(...)) with direct usage of createTheme(...)
  • Verified that theme configuration (palette, typography, spacing, etc.) uses MUI v5-compatible keys
  • Removed unused adaptV4Theme import

Result

  • No more deprecation warning from MUI
  • Theme structure is now future-proof and aligned with current MUI best practices

@jitsi-jenkins
Copy link

Hi, thanks for your contribution!
If you haven't already done so, could you please make sure you sign our CLA (https://jitsi.org/icla for individuals and https://jitsi.org/ccla for corporations)? We would unfortunately be unable to merge your patch unless we have that piece :(.

@saghul
Copy link
Member

saghul commented Aug 4, 2025

Does this have any practical implications?

@Zaid0412
Copy link
Contributor Author

Zaid0412 commented Aug 4, 2025

Does this have any practical implications?

Yes — it addresses the deprecation warning from MUI regarding adaptV4Theme() and helps future-proof the application.

Practical implications include:

  • Removing the dependency on deprecated MUI v4 compatibility logic
  • Preparing the theme configuration for full compatibility with MUI v5 and beyond, as adaptV4Theme() will eventually be phased out
  • Avoiding potentially subtle styling bugs caused by mismatches in theme formats

@saghul
Copy link
Member

saghul commented Aug 4, 2025

What I mean is: are there any implications such as visual changes because the change in theme structure?

@Zaid0412
Copy link
Contributor Author

Zaid0412 commented Aug 4, 2025

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.

Zaid0412 and others added 22 commits August 6, 2025 19:32
* 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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants