Mailerlite - Update to latest REST API version

[michelle0927]

Resolves #13964

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced new event sources for handling subscriber additions to groups and subscriber creations.

• Improvements

  • Enhanced data structure for subscriber-related actions, improving clarity and organization.
  • Updated descriptions and version numbers across several components for better documentation.

• Bug Fixes

  • Minor syntax improvements to streamline event emission logic for subscriber actions.

• Chores

  • Removed deprecated files that were no longer necessary for the integration.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
pipedream	❌ Failed (Inspect)			Sep 20, 2024 3:43am

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)	Visit Preview		Sep 20, 2024 3:43am
pipedream-docs	⬜️ Ignored (Inspect)			Sep 20, 2024 3:43am
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Sep 20, 2024 3:43am

[coderabbitai]

Walkthrough

The changes in this pull request involve updates across multiple MailerLite components, focusing on restructuring data handling for subscriber-related actions. Key modifications include version increments, rephrased descriptions for clarity, and adjustments to how parameters are passed in various methods. The overall aim is to enhance the organization and clarity of data interactions within the MailerLite API integration.

Changes

Files	Change Summary
components/mailerlite/actions/create-subscriber/create-subscriber.mjs, components/mailerlite/actions/list-subscribers/list-subscribers.mjs, components/mailerlite/actions/remove-subscriber-from-group/remove-subscriber-from-group.mjs, components/mailerlite/actions/subscribe-to-group/subscribe-to-group.mjs, components/mailerlite/actions/update-subscriber/update-subscriber.mjs	Updated version numbers, rephrased descriptions for clarity, and modified data structures for method calls to encapsulate parameters within objects, enhancing readability and maintainability.
components/mailerlite/mailerlite.app.mjs	Refactored API interaction logic to use Axios directly instead of the MailerLite SDK, simplifying the code structure and enhancing maintainability.
components/mailerlite/package.json	Updated version from 1.1.0 to 1.1.1, removed mailerlite-api-v2-node dependency, and added @pipedream/platform dependency.
components/mailerlite/sources/common/base.mjs	Modified the parameter structure for createHook and removeHook methods to enhance clarity in data being passed.
components/mailerlite/sources/subscriber-added-to-group/subscriber-added-to-group.mjs, components/mailerlite/sources/subscriber-added-to-group/test-event.mjs, components/mailerlite/sources/subscriber-created/subscriber-created.mjs, components/mailerlite/sources/subscriber-unsubscribed/subscriber-unsubscribed.mjs	Introduced new event sources and modified existing ones for subscriber actions, including updates to event emission logic and simplifications in returned objects.
components/mailerlite/sources/subscriber-added-from-form/subscriber-added-from-form.mjs, components/mailerlite/sources/subscriber-added-from-form/test-event.mjs	Deleted files related to handling subscriber addition through forms, indicating a shift in functionality.

Assessment against linked issues

Objective	Addressed	Explanation
Working components (related to HTTP errors) (#13964)	✅

Possibly related PRs

• New Components - krispcall #13867: Changes in subscriber data handling may relate to the restructuring in the create-subscriber action.
• Gmail usability pt.2 #13868: Modifications could connect with Gmail usability improvements if they involve similar data handling.
• New Components - agrello #13875: Introduction of new components for managing documents may relate to subscriber data processing changes.
• Toggl Client & Project Creation #13884: Toggl client updates may connect with changes involving user interactions and data structuring.
• New Components - adhook #13935: Changes in Adhook components may relate to structured data handling similar to subscriber updates.

Suggested labels

bug

Poem

🐰 In the meadow where the data flows,
Changes sprout like blooming rows.
Subscribers dance in structured grace,
With clarity now, they find their place.
Hops of joy, let updates ring,
In MailerLite's garden, we celebrate spring! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[michelle0927]

/approve