Skip to content

Commit d6131d7

Browse files
DavidsonGomesDavidsonGomes
committed
Merge branch 'release/2.2.1'
2 parents 633ab8b + 2228d58 commit d6131d7

File tree

94 files changed

+16751
-540
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

94 files changed

+16751
-540
lines changed

‎.env.example‎

Lines changed: 42 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ SERVER_URL=http://localhost:8080
55

66
SENTRY_DSN=
77

8-
TZ=America/Sao_Paulo
9-
108
# Cors - * for all or set separate by commas - ex.: 'yourdomain1.com, yourdomain2.com'
119
CORS_ORIGIN=*
1210
CORS_METHODS=GET,POST,PUT,DELETE
@@ -28,10 +26,10 @@ DEL_INSTANCE=false
2826

2927
# Provider: postgresql | mysql
3028
DATABASE_PROVIDER=postgresql
31-
DATABASE_CONNECTION_URI='postgresql://user:pass@localhost:5432/evolution?schema=public'
29+
DATABASE_CONNECTION_URI='postgresql://user:pass@postgres:5432/evolution?schema=public'
3230
# Client name for the database connection
3331
# It is used to separate an API installation from another that uses the same database.
34-
DATABASE_CONNECTION_CLIENT_NAME=evolution
32+
DATABASE_CONNECTION_CLIENT_NAME=evolution_exchange
3533

3634
# Choose the data you want to save in the application's database
3735
DATABASE_SAVE_DATA_INSTANCE=true
@@ -43,6 +41,7 @@ DATABASE_SAVE_DATA_LABELS=true
4341
DATABASE_SAVE_DATA_HISTORIC=true
4442
DATABASE_SAVE_IS_ON_WHATSAPP=true
4543
DATABASE_SAVE_IS_ON_WHATSAPP_DAYS=7
44+
DATABASE_DELETE_MESSAGE=true
4645

4746
# RabbitMQ - Environment variables
4847
RABBITMQ_ENABLED=false
@@ -90,6 +89,41 @@ SQS_REGION=
9089
WEBSOCKET_ENABLED=false
9190
WEBSOCKET_GLOBAL_EVENTS=false
9291

92+
# Pusher - Environment variables
93+
PUSHER_ENABLED=false
94+
PUSHER_GLOBAL_ENABLED=false
95+
PUSHER_GLOBAL_APP_ID=
96+
PUSHER_GLOBAL_KEY=
97+
PUSHER_GLOBAL_SECRET=
98+
PUSHER_GLOBAL_CLUSTER=
99+
PUSHER_GLOBAL_USE_TLS=true
100+
# Choose the events you want to send to Pusher
101+
PUSHER_EVENTS_APPLICATION_STARTUP=true
102+
PUSHER_EVENTS_QRCODE_UPDATED=true
103+
PUSHER_EVENTS_MESSAGES_SET=true
104+
PUSHER_EVENTS_MESSAGES_UPSERT=true
105+
PUSHER_EVENTS_MESSAGES_EDITED=true
106+
PUSHER_EVENTS_MESSAGES_UPDATE=true
107+
PUSHER_EVENTS_MESSAGES_DELETE=true
108+
PUSHER_EVENTS_SEND_MESSAGE=true
109+
PUSHER_EVENTS_CONTACTS_SET=true
110+
PUSHER_EVENTS_CONTACTS_UPSERT=true
111+
PUSHER_EVENTS_CONTACTS_UPDATE=true
112+
PUSHER_EVENTS_PRESENCE_UPDATE=true
113+
PUSHER_EVENTS_CHATS_SET=true
114+
PUSHER_EVENTS_CHATS_UPSERT=true
115+
PUSHER_EVENTS_CHATS_UPDATE=true
116+
PUSHER_EVENTS_CHATS_DELETE=true
117+
PUSHER_EVENTS_GROUPS_UPSERT=true
118+
PUSHER_EVENTS_GROUPS_UPDATE=true
119+
PUSHER_EVENTS_GROUP_PARTICIPANTS_UPDATE=true
120+
PUSHER_EVENTS_CONNECTION_UPDATE=true
121+
PUSHER_EVENTS_LABELS_EDIT=true
122+
PUSHER_EVENTS_LABELS_ASSOCIATION=true
123+
PUSHER_EVENTS_CALL=true
124+
PUSHER_EVENTS_TYPEBOT_START=false
125+
PUSHER_EVENTS_TYPEBOT_CHANGE_STATUS=false
126+
93127
# WhatsApp Business API - Environment variables
94128
# Token used to validate the webhook on the Facebook APP
95129
WA_BUSINESS_TOKEN_WEBHOOK=evolution
@@ -190,6 +224,10 @@ S3_USE_SSL=true
190224
# S3_USE_SSL=true
191225
# S3_REGION=eu-south
192226

227+
# Evolution Audio Converter - Environment variables - https://github.com/EvolutionAPI/evolution-audio-converter
228+
# API_AUDIO_CONVERTER=http://localhost:4040/process-audio
229+
# API_AUDIO_CONVERTER_KEY=429683C4C977415CAAFCCE10F7D57E11
230+
193231
# Define a global apikey to access all instances.
194232
# OBS: This key must be inserted in the request header to create an instance.
195233
AUTHENTICATION_API_KEY=429683C4C977415CAAFCCE10F7D57E11

‎.eslintrc.js‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,11 @@
11
module.exports = {
22
parser: '@typescript-eslint/parser',
33
parserOptions: {
4-
sourceType: 'CommonJS',
4+
project: 'tsconfig.json',
5+
tsconfigRootDir: __dirname,
6+
sourceType: 'module',
7+
warnOnUnsupportedTypeScriptVersion: false,
8+
EXPERIMENTAL_useSourceOfProjectReferenceRedirect: true,
59
},
610
plugins: ['@typescript-eslint', 'simple-import-sort', 'import'],
711
extends: ['eslint:recommended', 'plugin:@typescript-eslint/recommended', 'plugin:prettier/recommended'],

‎.github/ISSUE_TEMPLATE/-en--bug-report.yaml‎

Lines changed: 107 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,107 @@
1+
name: Bug Report
2+
description: Create a report to help us improve.
3+
labels:
4+
- bug
5+
- en
6+
# - help wanted
7+
# Automatically assign the issue to:
8+
# assignees: DavidsonGomes
9+
body:
10+
- type: checkboxes
11+
id: terms
12+
attributes:
13+
label: Welcome!
14+
description: |
15+
The issue tracker is only for reporting bugs and feature requests.
16+
For user-related support questions, please visit:
17+
- [Discord](https://evolution-api.com/discord)
18+
- [WhatsApp Group](https://evolution-api.com/whatsapp)
19+
<br/>
20+
21+
**DO NOT OPEN AN ISSUE FOR GENERAL SUPPORT QUESTIONS.**
22+
23+
options:
24+
- label: Yes, I have searched for similar issues on [GitHub](https://github.com/EvolutionAPI/evolution-api/issues) and found none.
25+
required: true
26+
27+
- type: textarea
28+
attributes:
29+
label: What did you do?
30+
description: |
31+
How to write a good bug report?
32+
33+
- Respect the issue template as much as possible.
34+
- The title should be short and descriptive.
35+
- Explain the conditions that led you to report this issue: the context.
36+
- The context should lead to something, an idea or problem you are facing.
37+
- Be clear and concise.
38+
- Format your messages to help the reader focus on what matters and understand the structure of your message, use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown)
39+
placeholder: Describe the problem you encountered in detail.
40+
validations:
41+
required: true
42+
43+
- type: textarea
44+
attributes:
45+
label: What did you expect?
46+
placeholder: Describe what you expected to happen.
47+
validations:
48+
required: true
49+
50+
- type: textarea
51+
attributes:
52+
label: What did you observe instead of what you expected?
53+
placeholder: Explain what actually happens when you follow the steps above.
54+
validations:
55+
required: true
56+
57+
- type: textarea
58+
attributes:
59+
label: Screenshots/Videos
60+
placeholder: |
61+
If possible, add screenshots or videos that illustrate the problem. This can be extremely helpful in understanding the issue better.
62+
63+
- type: textarea
64+
attributes:
65+
label: Which version of the API are you using?
66+
description: |
67+
Enter the version number found in the `version` property of the **package.json**.
68+
placeholder: Paste the version here.
69+
validations:
70+
required: true
71+
72+
- type: dropdown
73+
id: select
74+
attributes:
75+
label: What is your environment?
76+
options:
77+
- Windows
78+
- Linux
79+
- Mac
80+
- Docker
81+
- Other
82+
validations:
83+
required: true
84+
85+
- type: textarea
86+
attributes:
87+
label: Other environment specifications
88+
placeholder: 'Hardware/Software: [e.g., CPU, GPU]'
89+
validations:
90+
required: false
91+
92+
- type: textarea
93+
attributes:
94+
label: If applicable, paste the log output
95+
description: |
96+
Please attach any logs that might be related to the issue.
97+
If the logs contain sensitive information, consider sending them privately to one of the project maintainers.
98+
placeholder: Paste the application log here.
99+
validations:
100+
required: false
101+
102+
- type: textarea
103+
attributes:
104+
label: Additional Notes
105+
description: Include any other information you think might be useful to understand or resolve the bug.
106+
validations:
107+
required: false

‎.github/ISSUE_TEMPLATE/-en--feature-request.yaml‎

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
name: Feature Request
2+
description: Suggest ideas for the project.
3+
labels:
4+
- enhancement
5+
- en
6+
# Automatically assign the issue to:
7+
# assignees: DavidsonGomes
8+
body:
9+
- type: checkboxes
10+
id: terms
11+
attributes:
12+
label: Welcome!
13+
description: '**DO NOT OPEN FOR GENERAL SUPPORT QUESTIONS.**'
14+
15+
options:
16+
- label: Yes, I have searched for similar requests on [GitHub](https://github.com/code-chat-br/whatsapp-api/issues) and found none.
17+
required: true
18+
19+
- type: dropdown
20+
attributes:
21+
label: What type of feature?
22+
description: |
23+
How to write a good feature request?
24+
25+
- Respect the issue template as much as possible.
26+
- The title should be short and descriptive.
27+
- Explain the conditions that led you to suggest this feature: the context.
28+
- The context should lead to something, an idea or problem you are facing.
29+
- Be clear and concise.
30+
- Format your messages to help the reader focus on what matters and understand the structure of your message, use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown)
31+
options:
32+
- Integration
33+
- Functionality
34+
- Endpoint
35+
- Database adjustment
36+
- Other
37+
validations:
38+
required: true
39+
40+
- type: textarea
41+
attributes:
42+
label: What is the motivation for the request?
43+
description: |
44+
What problem does the feature seek to solve?
45+
Clearly and in detail describe the functionality you want to be implemented.
46+
Explain how it fits into the context of the project.
47+
placeholder: Detailed description
48+
validations:
49+
required: true
50+
51+
- type: textarea
52+
attributes:
53+
label: Usage Examples
54+
description: |
55+
Provide specific examples of how this functionality could be used.
56+
This can include scenarios or use cases where the feature would be particularly beneficial.
57+
placeholder: text - image - video - flowcharts
58+
validations:
59+
required: false
60+
61+
- type: textarea
62+
attributes:
63+
label: How should the feature be developed?
64+
description: |
65+
Should it be inserted directly into the code?
66+
Should it be built as a different application that acts as an extension of the API?
67+
For example: a `worker`?
68+
69+
Discuss how this new functionality could impact other parts of the project, if applicable.
70+
71+
---
72+
73+
If you have ideas on how this functionality could be implemented, please share them here.
74+
This is not mandatory, but it can be helpful for the development team.
75+
76+
placeholder: Insert feature ideas here
77+
validations:
78+
required: false
79+
80+
- type: textarea
81+
attributes:
82+
label: Additional Notes
83+
description: Any other information you believe is relevant to your request.
84+
placeholder: Insert your observations here.
85+
validations:
86+
required: false

‎.github/ISSUE_TEMPLATE/-pt--reportar-bug.yaml‎

Lines changed: 108 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,108 @@
1+
name: Relatório de bug
2+
description: Crie um relatório para nos ajudar a melhorar.
3+
labels:
4+
- bug
5+
- pt-br
6+
# - help wanted
7+
# Atrubuir automaticamente a issue a:
8+
# assignees: DavidsonGomes
9+
body:
10+
- type: checkboxes
11+
id: termos
12+
attributes:
13+
label: Bem-vido!
14+
description: |
15+
O rastreador de problemas é apenas para relatar bugs e solicitações de recursos.
16+
Para perguntas de suporte relacionadas ao usuário final, acesse:
17+
- [Discord](https://evolution-api.com/discord)
18+
- [Grupo do WhatsApp](https://evolution-api.com/whatsapp)
19+
<br/>
20+
21+
**NÃO ABRA UM PROBLEMA PARA PERGUNTAS GERAIS DE SUPORTE.**
22+
23+
options:
24+
- label: Sim, pesquisei problemas semelhantes no [GitHub](https://github.com/EvolutionAPI/evolution-api/issues) e não encontrei nenhum.
25+
required: true
26+
27+
- type: textarea
28+
attributes:
29+
label: O que você fez?
30+
description: |
31+
Como escrever um bom relatório de bug?
32+
33+
- Respeite o modelo de problema tanto quanto possível.
34+
- O título deve ser curto e descritivo.
35+
- Explique as condições que o levaram a reportar este problema: o contexto.
36+
- O contexto deve levar a algo, ideia ou problema que você está enfrentando.
37+
- Seja claro e conciso.
38+
- Formate suas mensagens para ajudar o leitor a se concentrar no que importa e entender a estrutura da sua mensagem, use [sintaxe Markdown](https://help.github.com/articles/github-flavored-markdown)
39+
placeholder: Descreva detalhadamente o problema que você encontrou.
40+
validations:
41+
required: true
42+
43+
- type: textarea
44+
attributes:
45+
label: O que você esperava?
46+
placeholder: Descreva o que você esperava que acontecesse.
47+
validations:
48+
required: true
49+
50+
- type: textarea
51+
attributes:
52+
label: O que vc observou ao invés do que esperava?
53+
placeholder: Explique o que realmente acontece quando você segue os passos acima.
54+
validations:
55+
required: true
56+
57+
- type: textarea
58+
attributes:
59+
label: Capturas de Tela/Vídeos
60+
placeholder: |
61+
Se possível, adicione capturas de tela ou vídeos que ilustrem o problema. Isso pode ser extremamente útil para entender melhor o problema.
62+
63+
- type: textarea
64+
attributes:
65+
label: Qual versão da API você está usando?
66+
description: |
67+
Insira o número da sua versão que está na propriedade `version` do **package.json**.
68+
placeholder: Cole aqui a versão.
69+
validations:
70+
required: true
71+
72+
- type: dropdown
73+
id: select
74+
attributes:
75+
label: Qual é o seu ambiente?
76+
options:
77+
- Windows
78+
- Linux
79+
- Mac
80+
- Docker
81+
- Outro
82+
validations:
83+
required: true
84+
85+
- type: textarea
86+
attributes:
87+
label: Outras expecificações do ambiente
88+
placeholder: 'Hardware/Software: [ex: CPU, GPU]'
89+
validations:
90+
required: false
91+
92+
- type: textarea
93+
attributes:
94+
label: Se aplicável, cole a saída do log
95+
description: |
96+
Por favor, anexe os logs que possam estar relacionados ao problema.
97+
Se os logs contiverem informações sensíveis, considere enviá-los de forma privada para um dos mantenedores do projeto.
98+
placeholder: Cole aqui o log da aplicação
99+
validations:
100+
required: false
101+
102+
- type: textarea
103+
attributes:
104+
label: Notas Adicionais
105+
description: Inclua aqui qualquer outra informação que você ache que possa ser útil para entender ou resolver o bug.
106+
validations:
107+
required: false
108+

0 commit comments

Comments
 (0)