Short.io improvements

[GTFalcao]

Closes #14216

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced new properties folderId and domainId for enhanced link management.
  • Added methods for fetching domain info and listing folder options.

• Updates

  • Updated metadata for several components, including names and descriptions for clarity.
  • Incremented version numbers across multiple components to reflect changes.

• Bug Fixes

  • No specific bug fixes were included in this release, but structural improvements were made for better functionality.

[vercel]

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

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)	Visit Preview		Oct 29, 2024 6:41pm
pipedream-docs	⬜️ Ignored (Inspect)			Oct 29, 2024 6:41pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Oct 29, 2024 6:41pm

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

📥 Commits

Files that changed from the base of the PR and between f004dcb and 062a0b3.

📒 Files selected for processing (8)

• components/short/actions/create-a-link/create-a-link.mjs (2 hunks)
• components/short/actions/delete-a-link/delete-a-link.mjs (1 hunks)
• components/short/actions/domain-statistics/domain-statistics.mjs (1 hunks)
• components/short/actions/expire-a-link/expire-a-link.mjs (1 hunks)
• components/short/actions/update-a-link/update-a-link.mjs (1 hunks)
• components/short/package.json (1 hunks)
• components/short/short.app.mjs (2 hunks)
• components/short/sources/new-link-created/new-link-created.mjs (1 hunks)

______________________________________________________________________________________________________________________________________________________________________________________________________________
< Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves. - Alan Kay >
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 \
  \   \
       \ /\
       ( )
     .( o ).

Tip

You can customize the tone of the review comments and chat replies.

Set the tone_instructions setting in your project's settings in CodeRabbit to customize the tone of the review comments and chat replies. For example, you can set the tone to Act like a strict teacher, Act like a pirate and more.

---

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.

[luancazarine]

Hi @GTFalcao, LGTM! Ready for QA!