own_2.2.3 version #1
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Update Docker image repository to evoapicloud/evolution-api - Modify contact email to contato@evolution-api.com - Update Docker Compose, Dockerfile, and workflow files - Add Docker image badge to README - Include additional content creator in README - Implement message deduplication cache in Baileys service
…leys service - Refactor edited message detection logic - Prevent duplicate message processing for edited messages - Optimize message key caching mechanism
…{baseUrl}}/chat/fetchCatalogs' and '{{baseUrl}}/chat/fetchCollections'
Refactor edit and delete message functionality in BaileyStartupService
Feat: Adicionei suporte para obter o Catálogos de Produtos e as Coleções de Produtos para a versão 2.2.3
- Added NATS package to dependencies - Created Prisma schema models for NATS configuration - Implemented NATS controller, router, and event management - Updated instance controller and event manager to support NATS - Added NATS configuration options in environment configuration - Included NATS events in instance validation schema
…gos de produtos e Coleções evitando alterações desnecessárias em arquivos do repositório
Adicionado suporte para obter Catálogos e Coleções no WhatsApp Business
feat: notconvertsticket for animated stickers
Fix instance creation on v2.2.3
…-location feat: add message location support whatsapp meta
Fix audio send duplicate from chatwoot.
…twoot fix: chatwoot csat creating new conversation in another language
…#1234 Corrige problema na API relacionado à migration. Fixes EvolutionAPI#1234
fix: change service image version and change to latest config session phone version
…age-params Update `fetchStatusMessage` to handle empty offset / page
fix: adjustment in audio transcription with official api
feat(audio): support LPCM and fix waveform distortion
…oggling status - Added null checks for conversation object in reopenConversation mode and when finding unresolved conversations. - Improved logging for better debugging of conversation retrieval.
- Added new dependency `audio-decode` version 2.2.3. - Introduced `@eshaz/web-worker` version 1.2.2 with its metadata. - Refactored `userDevicesCache` initialization and various object destructuring for improved readability in `whatsapp.baileys.service.ts`. - Streamlined multiple object property assignments for better code clarity. - Removed deprecated `@typescript-eslint/project-service` and related packages from package-lock.json.
…anced functionality - Introduced a new boolean parameter `isLid` in relevant methods to improve the handling of conversation data. - Updated conditionals to incorporate `isLid` for more precise data management. - Ensured backward compatibility by maintaining existing functionality while enhancing the service's capabilities.
…dels - Introduced `splitMessages` and `timePerChar` fields in the Typebot and TypebotSetting models with default values. - Created a migration script to update the database schema accordingly. - Updated audio message handling to prepend `[audio]` to transcriptions for better clarity in message context.
… processing - Updated media message preparation to conditionally include filename and caption based on media type. - Improved error handling in media ID retrieval and audio processing methods. - Refactored audio processing to support file uploads and URL handling more effectively. - Enhanced logging for better error tracking during media operations.
…ss property - Updated the token retrieval in the BusinessStartupService to use a class property instead of a hardcoded environment variable. - This change enhances flexibility and maintainability of the service configuration.
- Included `whatsappWebVersion` in the response object to provide the version of the WhatsApp web session from the environment configuration. - This addition enhances the API's response with relevant session information for clients.
…identifiers - Updated contact retrieval to handle cases where the identifier is not found, specifically for @lid scenarios. - Introduced a new method to normalize contact identifiers, prioritizing senderLid and participantLid. - Improved logging for better traceability during contact lookups and conversation handling.
…ders - Enhanced the logic for retrieving sender numbers by introducing a new method that prioritizes senderPn, followed by participant and remoteJid. - This change ensures more reliable identification of message senders across different scenarios.
- Introduced a new optional `lid` field in the IsOnWhatsapp model to enhance data tracking. - Updated migration script to add the `lid` column to the database. - Modified OnWhatsAppDto to include the `lid` property for better integration with WhatsApp user data. - Enhanced the WhatsApp Baileys service to handle `lid` numbers separately and improve user verification logic. - Updated cache handling functions to support the new `lid` field for consistent data management.
- Modified the root route to fetch the latest WhatsApp web version from Baileys if not set in the environment configuration. - This enhancement ensures that clients receive the most up-to-date version information in the API response.
- Updated the .env.example file to comment out the CONFIG_SESSION_PHONE_VERSION variable, indicating it is not currently set. This change helps clarify the configuration options available for users.
…version fetching logic - Added a new utility function `fetchLatestWaWebVersion` to retrieve the latest WhatsApp Web version. - Updated the Baileys service and router to utilize the new function instead of the deprecated `fetchLatestBaileysVersion`, ensuring accurate version information is fetched for WhatsApp integration. - This change enhances the reliability of version management in the application.
- Added support for `lid` in WhatsApp numbers router to improve contact identification. - Updated the contact retrieval logic to accept an object with `phone_number` and `identifier` for better clarity and consistency. - Enhanced error handling and logging in the Chatwoot service for improved traceability during contact creation and updates. - Implemented automatic search for the latest WhatsApp version if the CONFIG_SESSION_PHONE_VERSION variable is not set, ensuring users have the most up-to-date integration.
…djusts-treatment-lid-numbers refactor(chatwoot): Melhora e ajusta tratamento de números @lid
fix: ajuste na validacao dos bots e pausar sessao
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.