Rocket.Chat

The communications platform that puts data protection first.

hacktoberfest collaboration foss javascript meteor real-time webrtc mit slack chat free

History

Guilherme Gazzo e3d184bc4e Regression: Fix users.create call (#25834 ) <!-- 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
..
InfoPanel	Chore: Dedicated package for UI contexts (#25432 )	4 years ago
account	Chore: RestApiClient as Package (#25469 )	4 years ago
admin	Regression: Fix users.create call (#25834 )	4 years ago
banners	Chore: move definitions to packages (#25085 )	4 years ago
blocks	[FIX] Thread Message Preview (#25709 )	4 years ago
directory	Chore: RestApiClient as Package (#25469 )	4 years ago
e2e	Chore: Dedicated package for UI contexts (#25432 )	4 years ago
hooks	Chore: RestApiClient as Package (#25469 )	4 years ago
invite	Chore: RestApiClient as Package (#25469 )	4 years ago
location	Chore: Dedicated package for UI contexts (#25432 )	4 years ago
login	Chore: Dedicated package for UI contexts (#25432 )	4 years ago
mailer	Chore: Dedicated package for UI contexts (#25432 )	4 years ago
meet	Chore: RestApiClient as Package (#25469 )	4 years ago
notAuthorized	Chore: Dedicated package for UI contexts (#25432 )	4 years ago
notFound	Chore: remove duplicated NotFoundPage.js (#25749 )	4 years ago
omnichannel	[FIX] AgentsPage pagination (#25820 )	4 years ago
room	[FIX] `You and @yourUsername reacted with`title on reactions (#25733 )	4 years ago
root	Chore: Taking out Blaze from routes with `MainLayout` (#25697 )	4 years ago
setupWizard	Chore: RestApiClient as Package (#25469 )	4 years ago
teams	Chore: RestApiClient as Package (#25469 )	4 years ago