v1.1.1

⬆️ Upgrade bot-builder version

This release fixes a bug that made the bot crash when a message with the command symbol by itself was received.

Example:

Receiving a message ! without any content would make the bot crash, !a wouldn't.

Changelog:

• 🐛 Fix no command bug

Full Changelog: v1.1.0...v1.1.1

v1.1.0

✨ Add Map for Command Arguments

@totigm/bot-builder v1.2.0 introduced a feature to map command arguments to their respective values. This enhancement facilitates the efficient handling and retrieval of command argument data in a more structured manner.

Example:

From the message !command text="Hey there!" testing stage=development, an argsMap object is created. This object makes it easy to access the individual arguments and their values (or true if they are flags). Here's how the argsMap would look for this command:

{
    text: "Hey there!",
    testing: true,
    stage: "development"
}

Changelog:

• ⬆️ Update @totigm/bot-builder to v1.2.0
  • ✨ Add map for command arguments
  • 🎨 Improve argument parsing logic
  • ♻️ Refactor argument handling in formatMessage

Full Changelog: v1.0.14...v1.1.0 (see @totigm/bot-builder changelog)

v1.0.14

🏷️ Fix exported types

whatsapp-web.js and @totigm/bot-builder types weren't accessible by this library's consumers because of a problem with module.exports = WhatsappBot.

Changelog

• 🏷️ Fix exported types
  • Export whatsapp-web.js types fixed
  • Export @totigm/bot-builder types fixed

Full Changelog: v1.0.13...v1.0.14

v1.0.13

🏷️ Update exported types

Export whatsapp-web.js and @totigm/bot-builder so they can be used by this library's consumers

Changelog

• 🏷️ Update exported types
  • Export whatsapp-web.js types
  • Export @totigm/bot-builder types

Full Changelog: v1.0.12...v1.0.13

v1.0.12

⬆️ Update whatsapp-web.js version

Update whatsapp-web.js to v1.23.0.

Changelog

• ⬆️ Update whatsapp-web.js version
• 👽️ Skip lib check due to dependencies issues
  • whatsapp-web-js has some JSDoc issues that are making our build step crash

Full Changelog: v1.0.11...v1.0.12

v1.0.11

⬆️ Update whatsapp-web.js version

Update whatsapp-web.js to v1.19.5 to fix LegacyPhoneFeatures error

Changelog

• ⬆️ Update whatsapp-web.js version

Full Changelog: v1.0.10...v1.0.11

v1.0.10

⬆️ Update whatsapp-web.js version

Update whatsapp-web.js to v1.18.3 to fix GroupMetadata module

Changelog

• ⬆️ Update whatsapp-web.js version

Full Changelog: v1.0.9...v1.0.10

v1.0.9

⬆️ Update whatsapp-web.js version

Update whatsapp-web.js to v1.18.2 for proper compatibility with WhatsApp Web v2.2241.6

Changelog

• ⬆️ Update whatsapp-web.js version

Full Changelog: v1.0.8...v1.0.9

v1.0.8

⬆️ Update whatsapp-web.js version

Update whatsapp-web.js to v1.18.0 for proper compatibility with WhatsApp Web v2.2240.7.

Changelog

• ⬆️ Update whatsapp-web.js version
• 📝 Add reference to WhatsApp bot template

Full Changelog: v1.0.7...v1.0.8

v1.0.7

🧑‍💻 Add is docker env variable support

When deploying Dockerized apps to some cloud providers, such as Heroku, the .dockerenv file don't exist, so now the IS_DOCKER_CONTAINER environment variable is also checked to use Puppeteer settings that can be run on Docker containers.

Full Changelog: v1.0.6...v1.0.7