- Jan 31, 2025
-
-
Guilherme Gazzo authored
Co-authored-by:
Diego Sampaio <chinello@gmail.com> Co-authored-by:
Kevin Aleman <kaleman960@gmail.com>
-
- Jan 29, 2025
-
-
Tasso Evangelista authored
-
- Oct 19, 2024
-
-
Marcos Spessatto Defendi authored
Co-authored-by:
gabriellsh <gabriel.henriques@rocket.chat> Co-authored-by:
Guilherme Gazzo <guilhermegazzo@gmail.com>
-
- Sep 30, 2024
-
-
Pierre Lehnen authored
Co-authored-by:
Aleksander Nicacio da Silva <6494543+aleksandernsilva@users.noreply.github.com>
-
- Jul 30, 2024
-
-
Tasso Evangelista authored
-
- Jul 15, 2024
-
-
Rodrigo Nascimento authored
-
- Jun 18, 2024
-
-
dionisio-bot[bot] authored
Co-authored-by:
Guilherme Gazzo <5263975+ggazzo@users.noreply.github.com>
-
Guilherme Gazzo authored
-
- Apr 23, 2024
-
-
Guilherme Gazzo authored
-
- Apr 19, 2024
-
-
Matheus Barbosa Silva authored
Co-authored-by:
gabriellsh <40830821+gabriellsh@users.noreply.github.com>
-
- Nov 24, 2023
-
-
Guilherme Gazzo authored
-
- Aug 16, 2023
-
-
Tasso Evangelista authored
-
- Aug 09, 2023
-
-
Guilherme Gazzo authored
-
- Jul 19, 2023
-
-
Guilherme Gazzo authored
Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
- Jul 18, 2023
-
-
Guilherme Gazzo authored
-
Douglas Fabris authored
Co-authored-by:
Guilherme Gazzo <guilhermegazzo@gmail.com>
-
- Jul 14, 2023
-
-
Guilherme Gazzo authored
regression: Apply right filters to action buttons and convert `applyButtonFilters` to `useApplyButtonFilters` (#29822)
-
- Jul 11, 2023
-
-
Guilherme Gazzo authored
Co-authored-by:
Tasso Evangelista <tasso.evangelista@rocket.chat>
-
- Jul 07, 2023
-
-
Guilherme Gazzo authored
-
- Jul 06, 2023
-
-
Guilherme Gazzo authored
-
- May 30, 2023
-
-
Guilherme Gazzo authored
-
- May 26, 2023
-
-
Guilherme Gazzo authored
-
- May 08, 2023
-
-
Guilherme Gazzo authored
Co-authored-by:
Tasso Evangelista <tasso.evangelista@rocket.chat>
-
- Apr 01, 2023
-
-
Tasso Evangelista authored
-
- Mar 30, 2023
-
-
Tasso Evangelista authored
-
- Jun 28, 2022
-
-
Tasso Evangelista authored
<!-- 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. --> - Everything inside a new package (`@rocket.chat/gazzodown`); - KaTeX support; - Highlighted Words support; - Emoji rendering expanded; - Code rendering fixed <!-- 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... -->
-
- Apr 13, 2022
-
-
Guilherme Gazzo authored
-