Rocket.Chat

Commit Graph

Author	SHA1	Message	Date
souzaramon	668e6d4ec8	Revert "Chore: Collect e2e coverage (#25743 )" (#25936 ) This reverts commit `e43d0d2b79`.	4 years ago
souzaramon	e43d0d2b79	Chore: Collect e2e coverage (#25743 ) ## Proposed changes - collect e2e coverage - publish to artifacts - publish badges to gh-pages	4 years ago
Tasso Evangelista	0862751801	Chore: Replace `useSubscription` with `useSyncExternalStore` (#25909 ) <!-- 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
Diego Sampaio	eedc18b3d9	Chore: Run tests on docker (#25556 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	4 years ago
Pierre Lehnen	610670cadf	[NEW] Create Team with a member list of usernames (#25868 ) <!-- 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: Douglas Fabris <27704687+dougfabris@users.noreply.github.com>	4 years ago
Marcos Spessatto Defendi	42ae7aa829	Chore: Convert assets endpoint to Typescript (#25358 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com> Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>	4 years ago
Guilherme Gazzo	6b6f9dcb74	Chore: Convert users endpoints (#25635 ) Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz> Co-authored-by: Tasso Evangelista <tasso.evangelista@rocket.chat>	4 years ago
souzaramon	45b6640f41	Chore: create a e2e test guideline (#25884 ) ## Proposed changes (including videos or screenshots) - Create a e2e guideline	4 years ago
Douglas Fabris	c03dd9e657	[FIX] Kebab menu clicking issue (#25869 ) Co-authored-by: Tasso Evangelista <tasso.evangelista@rocket.chat>	4 years ago
souzaramon	bff2f4af8a	Chore: update pageobjects to use es6 getters and remove export default (#25867 ) ## Proposed changes (including videos or screenshots) - Simplify imports of pageobjects - Refactor pageobjects to use es6 getters - Move BagePage stuff to Global page object	4 years ago
souzaramon	666740adb5	Chore: remove unused locators from e2e tests (#25860 ) ## Proposed changes (including videos or screenshots) - Remove unused locators	4 years ago
Douglas Fabris	949fcae919	Chore: Rewrite Admin UsersTable to Typescript (#25698 ) <!-- 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
Yash Rajpal	813883181a	Chore: RouteGroup for My Account sidebar (#25632 ) <!-- 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. --> Refactoring My Accounts routes. Allows to add "my account" routes for EE. <!-- 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: Douglas Fabris <27704687+dougfabris@users.noreply.github.com>	4 years ago
Weslley Campos	0d8a2aa2a6	Chore: Add tests for agents screens (#25637 ) <!-- 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) Add some tests for omnichannel agents screen and add some data-qa in components f <!-- 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
Murtaza Patrawala	5a74a5c164	[FIX] Voip endpoint permissions (#25783 ) <!-- 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 --> Earlier we didn't check for any permissions while creating or closing VoIP room. This new PR will enforce those permission checks ## 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
Fábio Albuquerque	150c6b4a63	Chore: API test on method GET with params as a number. (#25769 )	4 years ago
Felipe	afcbf1c52e	Chore: convert invites, misc and subscriptions to TS and create definitions (#25350 )	4 years ago
Douglas Fabris	264f55098d	[NEW] Fuselage ToastBar (#25583 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com> Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>	4 years ago
Marcos Spessatto Defendi	e682030213	[IMPROVE] Refactor + unit tests for federation-v2 (#25680 ) * refactor: refactor matrix bridge to support testing + unit tests * fix: fix conflict * fix: types on test * fix: fix tests * chore: rename bridged to federated * chore: remove duplicated config * fix: fix yarn.lock * chore: add migration for the renamed field * chore: fix lint * fix: type	4 years ago
Felipe	0b1073ecde	Chore: add Ajv JSON Schema to api/v1 (#25601 )	4 years ago
Weslley Campos	cbabcc5d1f	Chore: Test for department screen (#25696 )	4 years ago
souzaramon	48bf450e14	Chore: Remove all cypress tests, configs and references (#25564 )	4 years ago
Weslley Campos	7158239927	Chore: adjust in some configurations (#25612 )	4 years ago
Weslley Campos	1a61ed1d53	Chore: migrate-to-pw-16-discussion (#25567 )	4 years ago
Tasso Evangelista	5b81dbad63	Chore: Migrate some small helper functions to TypeScript (#25666 )	4 years ago
Guilherme Gazzo	31ae30f30a	Chore: Rest API query parameters handling (#25648 )	4 years ago
Fábio Albuquerque	574e82d887	Chore: Rewrite im and dm endpoints to ts (#25521 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	4 years ago
Guilherme Gazzo	529295773a	Chore: Dependencies upgrade (#25290 )	4 years ago
Pierre Lehnen	6aa09ecc17	[FIX] Integrations avatar attribute misuse (#25283 )	4 years ago
souzaramon	e8512977d3	Test: Migrate 13-permissions from cypress to playwright (#25558 )	4 years ago
Weslley Campos	3ab9d8a492	Chore: migrate-to-pw-adjust-in-intermitences (#25542 )	4 years ago
Weslley Campos	fd40e3e6cb	Chore: migrate from cypress to pw 14-setting-permission (#25523 )	4 years ago
souzaramon	88710b290c	Chore: Tests with Playwright (task: ROC-31, 12-settings) (#25253 )	4 years ago
souzaramon	72db7a246a	Chore: Migrate 15-message-popup from cypress to playwright (#25462 )	4 years ago
Douglas Fabris	216301c934	[IMPROVE] New admin settings Page (#25439 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	4 years ago
Guilherme Gazzo	54a3887582	Chore: REST query and body params validation (#25446 )	4 years ago
Weslley Campos	dab6fb3d21	Chore: Tests with Playwright (task: ROC-66, Intermittent resolution in tests) (#25416 ) Co-authored-by: Ramon Souza <ramon.souza@objective.com.br>	4 years ago
Tasso Evangelista	cb0c4063f6	Chore: Dedicated package for UI contexts (#25432 )	4 years ago
Weslley Campos	a5abdda180	Chore: Tests with Playwright (task: ROC-25, 06-message) (#25252 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	4 years ago
gabriellsh	0d3f534c1a	Regression: Change preference to be default legacy messages (#25255 )	4 years ago
Alan Sikora	774f52671b	[NEW] Alpha Matrix Federation (#23688 ) Implement alpha support for Matrix Federation Co-authored-by: Aaron Ogle <aaron@geekgonecrazy.com> Co-authored-by: Marcos Defendi <marcos.defendi@ulbra.inf.br> Co-authored-by: Rodrigo Nascimento <rodrigoknascimento@gmail.com>	4 years ago
Tiago Ulisses Montini	ad1f974c0a	Chore: Tests with Playwright (task: ROC-28, 09-channels) (#25196 )	4 years ago
Guilherme Gazzo	977f167faa	Chore: move definitions to packages (#25085 )	4 years ago
Weslley Campos	fbd8337608	Chore: Tests with Playwright (task: All works) (#25122 )	4 years ago
Diego Sampaio	3d868250ea	Chore: Remove old files from removed Omnichannel feature (#25129 )	4 years ago
Diego Sampaio	961c06014e	First move to monorepo	4 years ago

47 Commits (dfd1d77674a4a40acea397e50f4fa5355aeaebe2)