Rocket.Chat

Commit Graph

Author	SHA1	Message	Date
Tasso Evangelista	d77894ce26	chore: Enforce stricter TypeScript directives (#37709 ) Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>	3 weeks ago
Guilherme Gazzo	b2d864c568	chore: update eslint plugins (#33879 )	1 year ago
Guilherme Gazzo	7dc9c4154f	chore: replace Meteor._localStorage -> Accounts.storageLocation (#33356 )	1 year ago
Tasso Evangelista	7aa0d963bb	chore(eslint): Unify ESLint configuration (#29896 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	2 years ago
Guilherme Gazzo	40cebcc0f1	chore: Move 2fa challenge handler to rest api package (#29263 )	3 years ago
Rodrigo Nascimento	5ad19c3f56	refactor(Meteor.user): Remove all occurrences (#28647 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	3 years ago
Tasso Evangelista	05a9c0101d	Chore: Unused/dead code removal (#28155 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	3 years ago
Murtaza Patrawala	a47e729f5b	[FIX] Toast notification ignoring 403 errors (#27624 )	3 years ago
Yash Rajpal	aa6a80b619	[NEW][ENTERPRISE] Device Management (#25791 ) Co-authored-by: Fábio Albuquerque <albuquerquefabio@icloud.com> Co-authored-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat> Co-authored-by: dougfabris <devfabris@gmail.com> Co-authored-by: csuadev <72958726+csuadev@users.noreply.github.com> Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz> Co-authored-by: Diego Sampaio <chinello@gmail.com> Co-authored-by: Pierre Lehnen <55164754+pierre-lehnen-rc@users.noreply.github.com> Co-authored-by: Murtaza Patrawala <34130764+murtaza98@users.noreply.github.com> Co-authored-by: Tasso Evangelista <tasso.evangelista@rocket.chat> Co-authored-by: Fábio Albuquerque <fabiosk881@gmail.com> Co-authored-by: Pierre Lehnen <pierre.lehnen@rocket.chat>	4 years ago
Tasso Evangelista	3427e5ed84	Chore: `refactor/tsc-perf` (#26040 ) Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz> Co-authored-by: Pierre Lehnen <pierre.lehnen@rocket.chat> Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	4 years ago
Yash Rajpal	750f0ef5b1	Regression: TOTP Modal with new rest api package (#25893 ) <!-- 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

12 Commits (develop)