freshdesk.getTicket: fix output mapping

[vtalas]

Summary by CodeRabbit

• New Features

  • Introduced a trigger for handling ticket deletion events.

• Bug Fixes

  • Resolved an issue affecting the ticket retrieval output.

• Chores

  • Updated the application version to 1.1.1 with revised release entries.

[coderabbitai]

Walkthrough

The changes update the application version in bundle.json from "1.1.0" to "1.1.1". The changelog has been modified to remove the old entry and add a new entry detailing the inclusion of a "DeletedTicket" trigger and a fix for the "Get Ticket" output port. In addition, the JSON configuration for the GetTicket component has been updated by renaming the embed fields property from "getTicketEmbedFields" to "embedFields".

Changes

File(s)	Change Summary
src/appmixer/freshdesk/bundle.json	Updated application version from "1.1.0" to "1.1.1". Removed the changelog entry for "1.1.0" and added a new entry for "1.1.1" with details on the DeletedTicket trigger and a fix for the Get Ticket output port.
src/appmixer/freshdesk/tickets/GetTicket/...	Renamed the property "getTicketEmbedFields" to "embedFields" in the JSON configuration for the GetTicket component, modifying the key in the output port data.

Suggested reviewers

• sayam-nasir

Poem

I’m a little rabbit with a knack for change,
Hopping through updates on a vibrant range.
Versions leap forward, fields renamed with flair,
In the code garden, improvements bloom everywhere.
With twitching whiskers and a joyful heart today,
I celebrate these changes in a bunny’s playful way!
🐇✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/appmixer/freshdesk/bundle.json (1)

17-19: Updated Changelog Entry

The new changelog entry for version "1.1.1" correctly documents the addition of the "DeletedTicket" trigger and the fix for the "Get Ticket" output port. Please verify that the removal of the previous "1.1.0" entry is intentional and that the changelog remains consistent with your release strategy.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 13d681e and ef9c2c5.

📒 Files selected for processing (2)

• src/appmixer/freshdesk/bundle.json (2 hunks)
• src/appmixer/freshdesk/tickets/GetTicket/component.json (1 hunks)

🔇 Additional comments (2)

src/appmixer/freshdesk/bundle.json (1)

3-3: Version Bump Verification

The version has been correctly updated from "1.1.0" to "1.1.1". Ensure that any external documentation or dependency settings referencing the version are adjusted accordingly.

src/appmixer/freshdesk/tickets/GetTicket/component.json (1)

60-60: Embed Fields Property Rename

The property name in the output mapping has been updated from "getTicketEmbedFields" to "embedFields", which aligns with the expected data structure. Please confirm that all components consuming this output reference the new key.