Rocket.Chat

Commit Graph

Author	SHA1	Message	Date
Tasso Evangelista	400b31e2e8	refactor(client): Miscelaneous (#28732 )	3 years ago
Filipe Marins	813cdfbe45	[NEW] [EE] PDF Chat transcript for Omnichannel conversations (#27572 ) Co-authored-by: Kevin Aleman <kaleman960@gmail.com> Co-authored-by: Murtaza Patrawala <34130764+murtaza98@users.noreply.github.com> Co-authored-by: murtaza98 <murtaza.patrawala@rocket.chat> Co-authored-by: Diego Sampaio <chinello@gmail.com>	3 years ago
Diego Sampaio	b0a848a4f3	[BREAK] Update Meteor to 2.9 and NodeJS to 14.21.1 (#27639 ) Co-authored-by: Tasso Evangelista <tasso.evangelista@rocket.chat>	3 years ago
Diego Sampaio	9647793404	Chore: Move service definitions to core services package (#27546 )	3 years ago
Diego Sampaio	4f2895ac54	Chore: Update tsconfig base target to es2020 (#27552 )	3 years ago
Kevin Aleman	461a8e2fe0	Chore: Create service template (#27519 ) Co-authored-by: Diego Sampaio <chinello@gmail.com>	3 years ago
Tasso Evangelista	bff5d48459	Chore: Upgrade ESLint (#26132 )	3 years ago
Tasso Evangelista	1176ed4ee5	Regression: Align TypeScript version across workspaces (#26184 )	4 years ago
Guilherme Gazzo	3544ed0a73	Chore: Revert `yarn dev` implementation (#26075 )	4 years ago
gabriellsh	80ae54e3bf	Regression: `yarn dev` not working (#26071 )	4 years ago
gabriellsh	016584b599	[FIX] Too many watchers in dev environment. (#25930 ) <!-- 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
Tasso Evangelista	8634d3ca5a	[IMPROVE] Expand the feature set of the new message rendering (#25970 ) <!-- 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... -->	4 years ago
Pierre Lehnen	845f56e37d	Chore: Model Typings (#25758 ) Co-authored-by: Diego Sampaio <chinello@gmail.com>	4 years ago
gabriellsh	06043f52cc	Chore: Watch for package changes (#25910 ) <!-- 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. --> With the current `dev` pipeline, whenever we modify a package (e.g. `api-client`), we have to kill the meteor proccess and run `yarn dev` again in order for the changes to be compiled and the new output to be used by meteor. This has the drawback of taking a little longer to run the dev environment, since we can't cache a watched buid. In the other hand, it reduces the friction of modifying internal packages since we don't need to rebuild the project for changes to take effect. This will enable us to move more things to separate packages without affecting the dev experience too much. <!-- 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
Guilherme Gazzo	529295773a	Chore: Dependencies upgrade (#25290 )	4 years ago
Jorge Leite	ee1d14618f	Chore: Convert email inbox feature to TypeScript (#25298 ) * chore: email-inbox rest types * Fix email inbox types * Email inbox endpoints to TS * Fix email-inbox params * Chore: Lib emailInbox to ts * chore: migrate to typescript * chore: fix lint * chore: fix table sort * Fix endpoint types * Chore: methods to insert and update was splitted * Removed the wrong validation * Back to default types for sort and query * Purge build files before compile * Require some fields of `IEmailInbox` * Fix weird destructuring Co-authored-by: albuquerquefabio <albuquerquefabio@icloud.com> Co-authored-by: Tasso Evangelista <tasso.evangelista@rocket.chat>	4 years ago
Pierre Lehnen	e6be278f11	Regression: eslint not running on packages (#25305 ) * Regression: eslint not running on packages Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	4 years ago
Guilherme Gazzo	2a83680c23	Chore: Template to generate packages (#25174 ) Co-authored-by: Diego Sampaio <chinello@gmail.com>	4 years ago

18 Commits (Export-PDF-Transcript)