Rocket.Chat

Commit Graph

Author	SHA1	Message	Date
Douglas Fabris	f7d2e27eec	chore: `Table` in favor of `GenericTable` (#29628 )	3 years ago
Douglas Fabris	c197624093	chore: Remove old deprecated `GenericTable` in favor of v2 (#29594 )	3 years ago
Douglas Fabris	955fbbc215	chore: Add eslint `react-jsx-key` rule on client (#29581 )	3 years ago
Matheus Barbosa Silva	2c93a635e9	regression: submitting text in the LDAP User Search modal reloads the page (#29137 )	3 years ago
Douglas Fabris	3bd185722c	chore: Replace `NoResults` in favor of `States` component (#29007 )	3 years ago
Júlia Jaeger Foresti	b86b6d1295	chore: Modal form wrapper (#27778 ) Co-authored-by: Douglas Fabris <27704687+dougfabris@users.noreply.github.com>	3 years ago
Tasso Evangelista	7960ff94c0	[BREAK] Limit `underscore` usage and remove `underscore.string` (even from integration script sandboxes) (#28037 )	3 years ago
Diego Sampaio	b0a848a4f3	[BREAK] Update Meteor to 2.9 and NodeJS to 14.21.1 (#27639 ) Co-authored-by: Tasso Evangelista <tasso.evangelista@rocket.chat>	3 years ago
Tasso Evangelista	649aa72ddf	Chore: Update ESlint rules of client code (#27427 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	3 years ago
Felipe	1bb9ee554d	Chore: deprecate refreshClients methods (#26956 ) Co-authored-by: Guilherme Gazzo <5263975+ggazzo@users.noreply.github.com>	3 years ago
Debdut Chakraborty	192837428b	[FIX] incorrect error toast messages (#26320 ) Co-authored-by: Tasso Evangelista <tasso.evangelista@rocket.chat>	3 years ago
Douglas Fabris	ca9b6cf05b	Chore: ModalFooterControllers adoption (#26445 )	3 years ago
Tasso Evangelista	133aa101d7	[IMPROVE] Upgrade nivo and React Query (#26338 )	3 years ago
gabriellsh	f2c84629ee	Chore: Rewrite custom OAuth Modals to react (#26204 ) Co-authored-by: Douglas Fabris <27704687+dougfabris@users.noreply.github.com>	3 years ago
Martin Schoeler	b77c075462	[BREAK] use urlParams on omnichannel/agent/extension/ (#25982 ) <!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. --> <!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation --> <!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat - Lint and unit tests pass locally with my changes - I have added tests that prove my fix is effective or that my feature works (if applicable) - I have added necessary documentation (if applicable) - Any dependent changes have been merged and published in downstream modules --> ## Proposed changes (including videos or screenshots) <!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. --> <!-- END CHANGELOG --> ## Issue(s) <!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 --> ## Steps to test or reproduce <!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable --> ## Further comments <!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->	4 years ago
Júlia Jaeger Foresti	0246fe1128	Chore: Colors (#25969 ) <!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. --> <!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation --> <!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat - Lint and unit tests pass locally with my changes - I have added tests that prove my fix is effective or that my feature works (if applicable) - I have added necessary documentation (if applicable) - Any dependent changes have been merged and published in downstream modules --> ## Proposed changes (including videos or screenshots) <!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. --> <!-- END CHANGELOG --> ## Issue(s) <!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 --> ## Steps to test or reproduce <!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable --> ## Further comments <!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->	4 years ago
Guilherme Gazzo	d69caf1bdc	Revert "[BREAK] use urlParams on omnichannel/agent/extension/" (#25980 )	4 years ago
Martin Schoeler	90f65b3269	[BREAK] use urlParams on omnichannel/agent/extension/ (#25874 ) <!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. --> <!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation --> <!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat - Lint and unit tests pass locally with my changes - I have added tests that prove my fix is effective or that my feature works (if applicable) - I have added necessary documentation (if applicable) - Any dependent changes have been merged and published in downstream modules --> ## Proposed changes (including videos or screenshots) I've noted that our extensions api was not using the same pattern that we use for a lot of `GET`s and `DELETE`s. This will fix an issue when trying to remove an agent from a voip extension.	4 years ago
Júlia Jaeger Foresti	d408c31046	[NEW] Colors Palette - Buttons (#25626 ) <!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. --> <!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation --> <!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat - Lint and unit tests pass locally with my changes - I have added tests that prove my fix is effective or that my feature works (if applicable) - I have added necessary documentation (if applicable) - Any dependent changes have been merged and published in downstream modules --> ## Proposed changes (including videos or screenshots) <!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. --> <!-- END CHANGELOG --> ## Issue(s) <!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 --> ## Steps to test or reproduce <!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable --> ## Further comments <!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... --> Co-authored-by: Guilherme Gazzo <5263975+ggazzo@users.noreply.github.com>	4 years ago
Guilherme Gazzo	611c0b31fb	Chore: RestApiClient as Package (#25469 ) <!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. --> <!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation --> <!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat - Lint and unit tests pass locally with my changes - I have added tests that prove my fix is effective or that my feature works (if applicable) - I have added necessary documentation (if applicable) - Any dependent changes have been merged and published in downstream modules --> ## Proposed changes (including videos or screenshots) <!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. --> <!-- END CHANGELOG --> ## Issue(s) <!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 --> ## Steps to test or reproduce <!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable --> ## Further comments <!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... --> Co-authored-by: Tasso Evangelista <2263066+tassoevan@users.noreply.github.com>	4 years ago
Tasso Evangelista	cb0c4063f6	Chore: Dedicated package for UI contexts (#25432 )	4 years ago
Júlia Jaeger Foresti	9a91764ba4	Chore: Convert client/views/admin/settings/groups folder to ts (#25345 )	4 years ago
Kevin Aleman	d3db5477e0	[IMPROVE] Add support for filters on omnichannel/extensions endpoint	4 years ago
Guilherme Gazzo	977f167faa	Chore: move definitions to packages (#25085 )	4 years ago
Diego Sampaio	961c06014e	First move to monorepo	4 years ago

26 Commits (Export-PDF-Transcript)