Refactored and reorganised entire css/less files and logic. #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rcaferati
added a commit
that referenced
this pull request
May 24, 2015
Refactored and reorganised entire css/less files and logic.
engelgabriel
pushed a commit
that referenced
this pull request
Jun 14, 2015
merging Rocket.Chat current master
engelgabriel
added a commit
that referenced
this pull request
Sep 6, 2015
engelgabriel
pushed a commit
that referenced
this pull request
Dec 4, 2015
Updating to more current version
Closed
This was referenced Jun 5, 2016
engelgabriel
pushed a commit
that referenced
this pull request
Aug 31, 2016
Merge RocketChat develop
leolara
referenced
this pull request
in ClaseChat/app
Sep 26, 2016
robertsoakes
pushed a commit
to GuruLabs/Rocket.Chat
that referenced
this pull request
Oct 7, 2016
merge with upstream
engelgabriel
pushed a commit
that referenced
this pull request
Nov 4, 2016
issue #4798: add path prefix to sidenav layout
engelgabriel
pushed a commit
that referenced
this pull request
Jan 17, 2017
engelgabriel
pushed a commit
that referenced
this pull request
Mar 3, 2017
Pulling latest Rocket develop
kamushadenes
added a commit
to kamushadenes/Rocket.Chat
that referenced
this pull request
Mar 13, 2017
Merged
engelgabriel
pushed a commit
that referenced
this pull request
Mar 14, 2017
Make Integration scripts work with Sandstorm
Syirrus
pushed a commit
to Syirrus/Rocket.Chat
that referenced
this pull request
Mar 21, 2017
…nto clarapy-v4 * 'develop' of https://github.com/RocketChat/Rocket.Chat: (32 commits) Update HISTORY.md Fix previous commits Fix coffee indentation Fix url links Update requests.js Solves issue RocketChat#3 by validating image domain Solves issue RocketChat#2 using CSP Make Integration scripts work with Sandstorm LingoHub Update 🚀 fix RocketChat#6334 Solves issue RocketChat#1 at user input Improvements to multiline codeblock parsing Keep LingoHub ident style for JSON translations Screen sharing doesn't flip anymore update stylelint Hotfix closes RocketChat#6300 lint fix fix RocketChat#6226 Simple ignores the custom audio from being loaded open shoud open a private channel to ...
engelgabriel
pushed a commit
that referenced
this pull request
Jul 4, 2017
engelgabriel
pushed a commit
that referenced
this pull request
Sep 2, 2017
amolghode1981
added a commit
that referenced
this pull request
Mar 16, 2022
…kup.com/t/22xdyn5 Description : Though this workspace was fix the first issue, it was realised that there are few other issues which are dependent on this(Not all may have a clickup task associated). This commit also fixes following : 1. Voip button does not get disabled when the user state changes. This happens because the user gets updated whenever the state change happens, this causes useVoipClient to reload this reload causes the reinitialsation of voipUser which initialises the connection again. 2. PR #24752 : This PR fixes the icon display only when the extension associated with the user. This is also fixed as this was broken due to fix for #1. (THis was using user object, and we are now not using the user object directly in the useEffect for voipClient initialisation. 3. This fix broke the fact that whenever user gets associated with the agent, voip button gets active. But because we removed the use of user, This was broken too. This got fixed by the virtue of fixing #2, i.e using extension as a state. 4. Even though the association is deleted, agent was still receiving the call. This was because the SIP user was never unregistered and cleared when the association gets deleted. Fixed this issue by calling voipClient.stop() method. This would take care of unregistering if the UA is registered and then closing the webSocket.
casalsgh
pushed a commit
that referenced
this pull request
Mar 17, 2022
* Clickup task : https://app.clickup.com/t/25jwe53 Description : Whenever the user state is changed (Explicitly or automatically by the virtue of user's inactivity) Voip component gets reloaded. Also during the reload of the page, the Voip component gets initialised multiple times, causing multiple websockets opened to asterisk. This happens because of the following facts: 1. The useEffect of useVoipClient, which creates the Voip component had user in its dependency list. 2. Whenever any user property changes, it would cause the useEffect to trigger and execute the entire initialisation of voip component. 3. When state change happens, it triggers update on all the components. So OmnichannelCallToggleReady gets re-rendered, also useVoipClient causes reinitialisation (user state change). 4. Now, when the useEffect of OmnichannelCallToggleReady gets executed, voipClient.getRegistrarState(); value is not |registered| because the state change has caused reinitialisation of voip component, which is not registered. 5. So again, the phone button value gets reset, the agent becomes unavailable. Fix: Even though the user state may change, user identity does not change. SIP client reinitialisation should happen only when userId changes. So the fix is not to add the entire userObject in the dependency list of the useEffect of useVoipClient hook. Instead 1. Create a state userId. 2. Add another useEffect watching the user. Whenever user becomes available or any user change happens, update the userId 3. The useEffect which does the voip client initialisation, should have the userId in the dependency list. When this is done, the Voip initialisation will happen only when userId changes. * Clickup task : https://app.clickup.com/t/25jwe53 Description : Realised that we have useUserId hook. As we have this hook, removed the useEffect which fetches the userId from user. Also removed the state. Instead added a constant userId. * Clickup Tasks: https://app.clickup.com/t/25jwe53 and https://app.clickup.com/t/22xdyn5 Description : Though this workspace was fix the first issue, it was realised that there are few other issues which are dependent on this(Not all may have a clickup task associated). This commit also fixes following : 1. Voip button does not get disabled when the user state changes. This happens because the user gets updated whenever the state change happens, this causes useVoipClient to reload this reload causes the reinitialsation of voipUser which initialises the connection again. 2. PR #24752 : This PR fixes the icon display only when the extension associated with the user. This is also fixed as this was broken due to fix for #1. (THis was using user object, and we are now not using the user object directly in the useEffect for voipClient initialisation. 3. This fix broke the fact that whenever user gets associated with the agent, voip button gets active. But because we removed the use of user, This was broken too. This got fixed by the virtue of fixing #2, i.e using extension as a state. 4. Even though the association is deleted, agent was still receiving the call. This was because the SIP user was never unregistered and cleared when the association gets deleted. Fixed this issue by calling voipClient.stop() method. This would take care of unregistering if the UA is registered and then closing the webSocket.
KevLehman
pushed a commit
that referenced
this pull request
Mar 18, 2022
* Clickup task : https://app.clickup.com/t/25jwe53 Description : Whenever the user state is changed (Explicitly or automatically by the virtue of user's inactivity) Voip component gets reloaded. Also during the reload of the page, the Voip component gets initialised multiple times, causing multiple websockets opened to asterisk. This happens because of the following facts: 1. The useEffect of useVoipClient, which creates the Voip component had user in its dependency list. 2. Whenever any user property changes, it would cause the useEffect to trigger and execute the entire initialisation of voip component. 3. When state change happens, it triggers update on all the components. So OmnichannelCallToggleReady gets re-rendered, also useVoipClient causes reinitialisation (user state change). 4. Now, when the useEffect of OmnichannelCallToggleReady gets executed, voipClient.getRegistrarState(); value is not |registered| because the state change has caused reinitialisation of voip component, which is not registered. 5. So again, the phone button value gets reset, the agent becomes unavailable. Fix: Even though the user state may change, user identity does not change. SIP client reinitialisation should happen only when userId changes. So the fix is not to add the entire userObject in the dependency list of the useEffect of useVoipClient hook. Instead 1. Create a state userId. 2. Add another useEffect watching the user. Whenever user becomes available or any user change happens, update the userId 3. The useEffect which does the voip client initialisation, should have the userId in the dependency list. When this is done, the Voip initialisation will happen only when userId changes. * Clickup task : https://app.clickup.com/t/25jwe53 Description : Realised that we have useUserId hook. As we have this hook, removed the useEffect which fetches the userId from user. Also removed the state. Instead added a constant userId. * Clickup Tasks: https://app.clickup.com/t/25jwe53 and https://app.clickup.com/t/22xdyn5 Description : Though this workspace was fix the first issue, it was realised that there are few other issues which are dependent on this(Not all may have a clickup task associated). This commit also fixes following : 1. Voip button does not get disabled when the user state changes. This happens because the user gets updated whenever the state change happens, this causes useVoipClient to reload this reload causes the reinitialsation of voipUser which initialises the connection again. 2. PR #24752 : This PR fixes the icon display only when the extension associated with the user. This is also fixed as this was broken due to fix for #1. (THis was using user object, and we are now not using the user object directly in the useEffect for voipClient initialisation. 3. This fix broke the fact that whenever user gets associated with the agent, voip button gets active. But because we removed the use of user, This was broken too. This got fixed by the virtue of fixing #2, i.e using extension as a state. 4. Even though the association is deleted, agent was still receiving the call. This was because the SIP user was never unregistered and cleared when the association gets deleted. Fixed this issue by calling voipClient.stop() method. This would take care of unregistering if the UA is registered and then closing the webSocket.
AllanPazRibeiro
pushed a commit
that referenced
this pull request
Mar 18, 2022
* Clickup task : https://app.clickup.com/t/25jwe53 Description : Whenever the user state is changed (Explicitly or automatically by the virtue of user's inactivity) Voip component gets reloaded. Also during the reload of the page, the Voip component gets initialised multiple times, causing multiple websockets opened to asterisk. This happens because of the following facts: 1. The useEffect of useVoipClient, which creates the Voip component had user in its dependency list. 2. Whenever any user property changes, it would cause the useEffect to trigger and execute the entire initialisation of voip component. 3. When state change happens, it triggers update on all the components. So OmnichannelCallToggleReady gets re-rendered, also useVoipClient causes reinitialisation (user state change). 4. Now, when the useEffect of OmnichannelCallToggleReady gets executed, voipClient.getRegistrarState(); value is not |registered| because the state change has caused reinitialisation of voip component, which is not registered. 5. So again, the phone button value gets reset, the agent becomes unavailable. Fix: Even though the user state may change, user identity does not change. SIP client reinitialisation should happen only when userId changes. So the fix is not to add the entire userObject in the dependency list of the useEffect of useVoipClient hook. Instead 1. Create a state userId. 2. Add another useEffect watching the user. Whenever user becomes available or any user change happens, update the userId 3. The useEffect which does the voip client initialisation, should have the userId in the dependency list. When this is done, the Voip initialisation will happen only when userId changes. * Clickup task : https://app.clickup.com/t/25jwe53 Description : Realised that we have useUserId hook. As we have this hook, removed the useEffect which fetches the userId from user. Also removed the state. Instead added a constant userId. * Clickup Tasks: https://app.clickup.com/t/25jwe53 and https://app.clickup.com/t/22xdyn5 Description : Though this workspace was fix the first issue, it was realised that there are few other issues which are dependent on this(Not all may have a clickup task associated). This commit also fixes following : 1. Voip button does not get disabled when the user state changes. This happens because the user gets updated whenever the state change happens, this causes useVoipClient to reload this reload causes the reinitialsation of voipUser which initialises the connection again. 2. PR #24752 : This PR fixes the icon display only when the extension associated with the user. This is also fixed as this was broken due to fix for #1. (THis was using user object, and we are now not using the user object directly in the useEffect for voipClient initialisation. 3. This fix broke the fact that whenever user gets associated with the agent, voip button gets active. But because we removed the use of user, This was broken too. This got fixed by the virtue of fixing #2, i.e using extension as a state. 4. Even though the association is deleted, agent was still receiving the call. This was because the SIP user was never unregistered and cleared when the association gets deleted. Fixed this issue by calling voipClient.stop() method. This would take care of unregistering if the UA is registered and then closing the webSocket.
AllanPazRibeiro
pushed a commit
that referenced
this pull request
Mar 18, 2022
* Clickup task : https://app.clickup.com/t/25jwe53 Description : Whenever the user state is changed (Explicitly or automatically by the virtue of user's inactivity) Voip component gets reloaded. Also during the reload of the page, the Voip component gets initialised multiple times, causing multiple websockets opened to asterisk. This happens because of the following facts: 1. The useEffect of useVoipClient, which creates the Voip component had user in its dependency list. 2. Whenever any user property changes, it would cause the useEffect to trigger and execute the entire initialisation of voip component. 3. When state change happens, it triggers update on all the components. So OmnichannelCallToggleReady gets re-rendered, also useVoipClient causes reinitialisation (user state change). 4. Now, when the useEffect of OmnichannelCallToggleReady gets executed, voipClient.getRegistrarState(); value is not |registered| because the state change has caused reinitialisation of voip component, which is not registered. 5. So again, the phone button value gets reset, the agent becomes unavailable. Fix: Even though the user state may change, user identity does not change. SIP client reinitialisation should happen only when userId changes. So the fix is not to add the entire userObject in the dependency list of the useEffect of useVoipClient hook. Instead 1. Create a state userId. 2. Add another useEffect watching the user. Whenever user becomes available or any user change happens, update the userId 3. The useEffect which does the voip client initialisation, should have the userId in the dependency list. When this is done, the Voip initialisation will happen only when userId changes. * Clickup task : https://app.clickup.com/t/25jwe53 Description : Realised that we have useUserId hook. As we have this hook, removed the useEffect which fetches the userId from user. Also removed the state. Instead added a constant userId. * Clickup Tasks: https://app.clickup.com/t/25jwe53 and https://app.clickup.com/t/22xdyn5 Description : Though this workspace was fix the first issue, it was realised that there are few other issues which are dependent on this(Not all may have a clickup task associated). This commit also fixes following : 1. Voip button does not get disabled when the user state changes. This happens because the user gets updated whenever the state change happens, this causes useVoipClient to reload this reload causes the reinitialsation of voipUser which initialises the connection again. 2. PR #24752 : This PR fixes the icon display only when the extension associated with the user. This is also fixed as this was broken due to fix for #1. (THis was using user object, and we are now not using the user object directly in the useEffect for voipClient initialisation. 3. This fix broke the fact that whenever user gets associated with the agent, voip button gets active. But because we removed the use of user, This was broken too. This got fixed by the virtue of fixing #2, i.e using extension as a state. 4. Even though the association is deleted, agent was still receiving the call. This was because the SIP user was never unregistered and cleared when the association gets deleted. Fixed this issue by calling voipClient.stop() method. This would take care of unregistering if the UA is registered and then closing the webSocket.
AllanPazRibeiro
pushed a commit
that referenced
this pull request
Mar 18, 2022
* Clickup task : https://app.clickup.com/t/25jwe53 Description : Whenever the user state is changed (Explicitly or automatically by the virtue of user's inactivity) Voip component gets reloaded. Also during the reload of the page, the Voip component gets initialised multiple times, causing multiple websockets opened to asterisk. This happens because of the following facts: 1. The useEffect of useVoipClient, which creates the Voip component had user in its dependency list. 2. Whenever any user property changes, it would cause the useEffect to trigger and execute the entire initialisation of voip component. 3. When state change happens, it triggers update on all the components. So OmnichannelCallToggleReady gets re-rendered, also useVoipClient causes reinitialisation (user state change). 4. Now, when the useEffect of OmnichannelCallToggleReady gets executed, voipClient.getRegistrarState(); value is not |registered| because the state change has caused reinitialisation of voip component, which is not registered. 5. So again, the phone button value gets reset, the agent becomes unavailable. Fix: Even though the user state may change, user identity does not change. SIP client reinitialisation should happen only when userId changes. So the fix is not to add the entire userObject in the dependency list of the useEffect of useVoipClient hook. Instead 1. Create a state userId. 2. Add another useEffect watching the user. Whenever user becomes available or any user change happens, update the userId 3. The useEffect which does the voip client initialisation, should have the userId in the dependency list. When this is done, the Voip initialisation will happen only when userId changes. * Clickup task : https://app.clickup.com/t/25jwe53 Description : Realised that we have useUserId hook. As we have this hook, removed the useEffect which fetches the userId from user. Also removed the state. Instead added a constant userId. * Clickup Tasks: https://app.clickup.com/t/25jwe53 and https://app.clickup.com/t/22xdyn5 Description : Though this workspace was fix the first issue, it was realised that there are few other issues which are dependent on this(Not all may have a clickup task associated). This commit also fixes following : 1. Voip button does not get disabled when the user state changes. This happens because the user gets updated whenever the state change happens, this causes useVoipClient to reload this reload causes the reinitialsation of voipUser which initialises the connection again. 2. PR #24752 : This PR fixes the icon display only when the extension associated with the user. This is also fixed as this was broken due to fix for #1. (THis was using user object, and we are now not using the user object directly in the useEffect for voipClient initialisation. 3. This fix broke the fact that whenever user gets associated with the agent, voip button gets active. But because we removed the use of user, This was broken too. This got fixed by the virtue of fixing #2, i.e using extension as a state. 4. Even though the association is deleted, agent was still receiving the call. This was because the SIP user was never unregistered and cleared when the association gets deleted. Fixed this issue by calling voipClient.stop() method. This would take care of unregistering if the UA is registered and then closing the webSocket.
sampaiodiego
pushed a commit
that referenced
this pull request
Mar 21, 2022
* Clickup task : https://app.clickup.com/t/25jwe53 Description : Whenever the user state is changed (Explicitly or automatically by the virtue of user's inactivity) Voip component gets reloaded. Also during the reload of the page, the Voip component gets initialised multiple times, causing multiple websockets opened to asterisk. This happens because of the following facts: 1. The useEffect of useVoipClient, which creates the Voip component had user in its dependency list. 2. Whenever any user property changes, it would cause the useEffect to trigger and execute the entire initialisation of voip component. 3. When state change happens, it triggers update on all the components. So OmnichannelCallToggleReady gets re-rendered, also useVoipClient causes reinitialisation (user state change). 4. Now, when the useEffect of OmnichannelCallToggleReady gets executed, voipClient.getRegistrarState(); value is not |registered| because the state change has caused reinitialisation of voip component, which is not registered. 5. So again, the phone button value gets reset, the agent becomes unavailable. Fix: Even though the user state may change, user identity does not change. SIP client reinitialisation should happen only when userId changes. So the fix is not to add the entire userObject in the dependency list of the useEffect of useVoipClient hook. Instead 1. Create a state userId. 2. Add another useEffect watching the user. Whenever user becomes available or any user change happens, update the userId 3. The useEffect which does the voip client initialisation, should have the userId in the dependency list. When this is done, the Voip initialisation will happen only when userId changes. * Clickup task : https://app.clickup.com/t/25jwe53 Description : Realised that we have useUserId hook. As we have this hook, removed the useEffect which fetches the userId from user. Also removed the state. Instead added a constant userId. * Clickup Tasks: https://app.clickup.com/t/25jwe53 and https://app.clickup.com/t/22xdyn5 Description : Though this workspace was fix the first issue, it was realised that there are few other issues which are dependent on this(Not all may have a clickup task associated). This commit also fixes following : 1. Voip button does not get disabled when the user state changes. This happens because the user gets updated whenever the state change happens, this causes useVoipClient to reload this reload causes the reinitialsation of voipUser which initialises the connection again. 2. PR #24752 : This PR fixes the icon display only when the extension associated with the user. This is also fixed as this was broken due to fix for #1. (THis was using user object, and we are now not using the user object directly in the useEffect for voipClient initialisation. 3. This fix broke the fact that whenever user gets associated with the agent, voip button gets active. But because we removed the use of user, This was broken too. This got fixed by the virtue of fixing #2, i.e using extension as a state. 4. Even though the association is deleted, agent was still receiving the call. This was because the SIP user was never unregistered and cleared when the association gets deleted. Fixed this issue by calling voipClient.stop() method. This would take care of unregistering if the UA is registered and then closing the webSocket.
sampaiodiego
pushed a commit
that referenced
this pull request
Mar 21, 2022
* Clickup task : https://app.clickup.com/t/25jwe53 Description : Whenever the user state is changed (Explicitly or automatically by the virtue of user's inactivity) Voip component gets reloaded. Also during the reload of the page, the Voip component gets initialised multiple times, causing multiple websockets opened to asterisk. This happens because of the following facts: 1. The useEffect of useVoipClient, which creates the Voip component had user in its dependency list. 2. Whenever any user property changes, it would cause the useEffect to trigger and execute the entire initialisation of voip component. 3. When state change happens, it triggers update on all the components. So OmnichannelCallToggleReady gets re-rendered, also useVoipClient causes reinitialisation (user state change). 4. Now, when the useEffect of OmnichannelCallToggleReady gets executed, voipClient.getRegistrarState(); value is not |registered| because the state change has caused reinitialisation of voip component, which is not registered. 5. So again, the phone button value gets reset, the agent becomes unavailable. Fix: Even though the user state may change, user identity does not change. SIP client reinitialisation should happen only when userId changes. So the fix is not to add the entire userObject in the dependency list of the useEffect of useVoipClient hook. Instead 1. Create a state userId. 2. Add another useEffect watching the user. Whenever user becomes available or any user change happens, update the userId 3. The useEffect which does the voip client initialisation, should have the userId in the dependency list. When this is done, the Voip initialisation will happen only when userId changes. * Clickup task : https://app.clickup.com/t/25jwe53 Description : Realised that we have useUserId hook. As we have this hook, removed the useEffect which fetches the userId from user. Also removed the state. Instead added a constant userId. * Clickup Tasks: https://app.clickup.com/t/25jwe53 and https://app.clickup.com/t/22xdyn5 Description : Though this workspace was fix the first issue, it was realised that there are few other issues which are dependent on this(Not all may have a clickup task associated). This commit also fixes following : 1. Voip button does not get disabled when the user state changes. This happens because the user gets updated whenever the state change happens, this causes useVoipClient to reload this reload causes the reinitialsation of voipUser which initialises the connection again. 2. PR #24752 : This PR fixes the icon display only when the extension associated with the user. This is also fixed as this was broken due to fix for #1. (THis was using user object, and we are now not using the user object directly in the useEffect for voipClient initialisation. 3. This fix broke the fact that whenever user gets associated with the agent, voip button gets active. But because we removed the use of user, This was broken too. This got fixed by the virtue of fixing #2, i.e using extension as a state. 4. Even though the association is deleted, agent was still receiving the call. This was because the SIP user was never unregistered and cleared when the association gets deleted. Fixed this issue by calling voipClient.stop() method. This would take care of unregistering if the UA is registered and then closing the webSocket.
sampaiodiego
pushed a commit
that referenced
this pull request
Mar 21, 2022
* Clickup task : https://app.clickup.com/t/25jwe53 Description : Whenever the user state is changed (Explicitly or automatically by the virtue of user's inactivity) Voip component gets reloaded. Also during the reload of the page, the Voip component gets initialised multiple times, causing multiple websockets opened to asterisk. This happens because of the following facts: 1. The useEffect of useVoipClient, which creates the Voip component had user in its dependency list. 2. Whenever any user property changes, it would cause the useEffect to trigger and execute the entire initialisation of voip component. 3. When state change happens, it triggers update on all the components. So OmnichannelCallToggleReady gets re-rendered, also useVoipClient causes reinitialisation (user state change). 4. Now, when the useEffect of OmnichannelCallToggleReady gets executed, voipClient.getRegistrarState(); value is not |registered| because the state change has caused reinitialisation of voip component, which is not registered. 5. So again, the phone button value gets reset, the agent becomes unavailable. Fix: Even though the user state may change, user identity does not change. SIP client reinitialisation should happen only when userId changes. So the fix is not to add the entire userObject in the dependency list of the useEffect of useVoipClient hook. Instead 1. Create a state userId. 2. Add another useEffect watching the user. Whenever user becomes available or any user change happens, update the userId 3. The useEffect which does the voip client initialisation, should have the userId in the dependency list. When this is done, the Voip initialisation will happen only when userId changes. * Clickup task : https://app.clickup.com/t/25jwe53 Description : Realised that we have useUserId hook. As we have this hook, removed the useEffect which fetches the userId from user. Also removed the state. Instead added a constant userId. * Clickup Tasks: https://app.clickup.com/t/25jwe53 and https://app.clickup.com/t/22xdyn5 Description : Though this workspace was fix the first issue, it was realised that there are few other issues which are dependent on this(Not all may have a clickup task associated). This commit also fixes following : 1. Voip button does not get disabled when the user state changes. This happens because the user gets updated whenever the state change happens, this causes useVoipClient to reload this reload causes the reinitialsation of voipUser which initialises the connection again. 2. PR #24752 : This PR fixes the icon display only when the extension associated with the user. This is also fixed as this was broken due to fix for #1. (THis was using user object, and we are now not using the user object directly in the useEffect for voipClient initialisation. 3. This fix broke the fact that whenever user gets associated with the agent, voip button gets active. But because we removed the use of user, This was broken too. This got fixed by the virtue of fixing #2, i.e using extension as a state. 4. Even though the association is deleted, agent was still receiving the call. This was because the SIP user was never unregistered and cleared when the association gets deleted. Fixed this issue by calling voipClient.stop() method. This would take care of unregistering if the UA is registered and then closing the webSocket.
debdutdeb
added a commit
that referenced
this pull request
Nov 29, 2022
dougfabris
pushed a commit
that referenced
this pull request
Oct 23, 2023
debdutdeb
added a commit
that referenced
this pull request
Nov 17, 2023
ManojaD2004
added a commit
to ManojaD2004/Rocket.Chat
that referenced
this pull request
Feb 5, 2024
Refactored and reorganised entire css/less files and logic.
Yashraj7890
pushed a commit
to Yashraj7890/Rocket.Chat
that referenced
this pull request
Feb 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.