Rocket.Chat

Commit Graph

Author	SHA1	Message	Date
Tasso Evangelista	9af2c11d64	refactor: JSX automatic runtime (#34498 )	1 year ago
Tasso Evangelista	de596579c0	refactor(i18n): Use i18next‘s t-function (#33601 )	1 year ago
Tasso Evangelista	73808aad3a	Revert "refactor(i18n): Increase the adoption of `react-i18next` - Phase 1" (#33485 )	1 year ago
Tasso Evangelista	af202c7a62	Revert "refactor(i18n): Increase the adoption of `react-i18next` - Phase 1" (#33485 )	1 year ago
Tasso Evangelista	98b6a20901	refactor(i18n): Increase the adoption of `react-i18next` - Phase 1 (#33175 )	1 year ago
Tasso Evangelista	99524f27c2	refactor(client): Remove usage of `React.FC` type (#32760 )	2 years ago
Douglas Fabris	b9c7bce518	chore: Initial a11y tweaks (#30119 )	2 years ago
Guilherme Gazzo	39322413fb	chore: use pixels for margins and paddings (#30023 ) Co-authored-by: dougfabris <devfabris@gmail.com>	2 years ago
Henrique Guimarães Ribeiro	8d74caf47e	[BREAK] Marketplace standalone page and app request flow (#27389 ) Co-authored-by: dougfabris <devfabris@gmail.com> Co-authored-by: Júlia Jaeger Foresti <60678893+juliajforesti@users.noreply.github.com> Co-authored-by: Tiago Evangelista Pinto <tiago.evangelista@rocket.chat> Co-authored-by: Felipe <84182706+felipe-rod123@users.noreply.github.com> Co-authored-by: yash-rajpal <rajpal.yash03@gmail.com> Co-authored-by: Matheus Carmo <matheus.carmo@rocket.chat> Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com> Co-authored-by: Rafael Tapia <rafael.tapia@rocket.chat> Co-authored-by: Rodrigo Nascimento <rodrigoknascimento@gmail.com> Co-authored-by: Diego Sampaio <chinello@gmail.com>	3 years ago
Guilherme Gazzo	12cb1c815c	Chore: Refactor e2e selectors to use roles (#27582 ) Co-authored-by: Rodrigo Nascimento <rodrigoknascimento@gmail.com>	3 years ago
Douglas Fabris	86ea45e992	Chore: Remove Sidebar from Blaze (#27571 ) Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz> Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	3 years ago
Júlia Jaeger Foresti	677f61ee8d	Chore: Sidebar theme (#27426 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com> Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>	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
Guilherme Gazzo	4cd128073e	Chore: Apply correct fuselage color tokens (#27089 )	3 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
Júlia Jaeger Foresti	e01c8eac92	Chore: Convert MemoizedSetting, Setting, Section (#25572 ) <!-- 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
Jean Brito	6b41aa6207	Chore: Convert components/sidebar to TS (#25429 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	4 years ago
Diego Sampaio	961c06014e	First move to monorepo	4 years ago
Diego Sampaio	7632f12cfc	Chore: Prettier for us all (#24000 )	4 years ago
Júlia Jaeger Foresti	7ac5a2a647	Chore: Replace typography (#24021 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	4 years ago
Júlia Jaeger Foresti	76a4380c1f	Chore: Replace new typography (#23756 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	4 years ago
Tasso Evangelista	d8a24b044e	[NEW] New set of rules for client code (#21318 ) Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>	5 years ago

16 Commits (develop)