Rocket.Chat

Commit Graph

Author	SHA1	Message	Date
Rodrigo Nascimento	2171e1f55b	chore: Move some compatible changes back from meteor 3 branch (#29297 )	3 years ago
Heitor Tanoue	8dbf24129d	chore: convert Rooms Model Raw to TypeScript (#28260 ) Co-authored-by: matheusbsilva137 <matheus_barbosa137@hotmail.com>	3 years ago
Tasso Evangelista	b543e90e91	refactor: Bump TypeScript version (#28697 )	3 years ago
Diego Sampaio	a0f435888a	refactor(models): Use Messages Raw model (9/N) (#28693 )	3 years ago
Kevin Aleman	9ea35c8e45	refactor: move subscriptions 4x (#28548 )	3 years ago
Guilherme Gazzo	c31773947a	refactor: federation Promise.await 1/N (#28591 ) * ARCH-390 easy part convert sendmessage to async * move processWebhookMessage to async * executeTriggerUrl to async * triggerHandler reply to async * RocketChatIntegrationHandler constructor * createLivechatRoom * fix processWebhookMessage * .. * sendSuccessReplyMessage * 🙄 * moved federation service creation to async * rename folders to better readability * allowRoomSettingChange to async * saveRoomType * fix TS * 🙄 * Tests * undo allowMemberAction * unit tests	3 years ago
Guilherme Gazzo	0584e51146	refactor: checkUsernameAvailability to async (#28557 ) Co-authored-by: Rodrigo Nascimento <rodrigoknascimento@gmail.com>	3 years ago
Guilherme Gazzo	c9bbad728f	refactor: convert addUserToRoom to async (#28479 )	3 years ago
Diego Sampaio	8fbbf4171f	refactor(eslint): Add "no-floating-promises" eslint rule - Part 3 (#28435 ) Co-authored-by: Rodrigo Nascimento <rodrigoknascimento@gmail.com>	3 years ago
Diego Sampaio	9647793404	Chore: Move service definitions to core services package (#27546 )	3 years ago
Luciano Marcos Pierdona Junior	643e8186d7	[FIX] Unable to remove a user who joined a public team with a mention (#26218 ) Co-authored-by: Matheus Barbosa Silva <36537004+matheusbsilva137@users.noreply.github.com>	3 years ago
Tasso Evangelista	f74ba4e587	Chore: ESLint warnings (#26504 )	3 years ago
Diego Sampaio	21b81e9a96	Chore: Update Meteor 2.7.3 (#25991 )	4 years ago
Luciano Marcos Pierdona Junior	f448cccddb	[FIX] Update subscription on update team member (#25855 ) <!-- 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. --> Added update to subscription when a team member is updated on `teams.updateMember` <!-- 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
Pierre Lehnen	845f56e37d	Chore: Model Typings (#25758 ) Co-authored-by: Diego Sampaio <chinello@gmail.com>	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
Matheus Barbosa Silva	6eb84146e9	[BREAK] Deactivated team members are added to auto-join rooms (#25016 ) <!-- 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. --> - Do not add deactivated users to auto-join rooms. <!-- 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 --> 1. Create a new team and add a team member to it; 2. Go to Administration > Users and deactivate one of the team members; 3. Return to the team and add an auto-join channel/group. _Expected behavior:_ the deactivated user should not be added to the room. ## 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
Leonardo Ostjen Couto	b893ffdc20	[NEW] New stats rewrite (#25078 ) Co-authored-by: matheusbsilva137 <matheus_barbosa137@hotmail.com> Co-authored-by: Diego Sampaio <chinello@gmail.com>	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

21 Commits (Export-PDF-Transcript)