Farcaster branding change

[dominictayloruk]

What kind of change does this PR introduce?

Farcaster branding change from Warpcast. More info here https://farcaster.xyz/farcaster/0x3339d2b0

Why was this change needed?

Warpcast rebranded to Farcaster

Other information:

Checklist:

Put a "X" in the boxes below to indicate you have followed the checklist;

• [x ] I have read the CONTRIBUTING guide.
• [ x] I checked that there were not similar issues or PRs already open for this.
• [ x] This PR fixes just ONE issue (do not include multiple issues or types of change in the same PR) For example, don't try and fix a UI issue and include new dependencies in the same PR.

Summary by CodeRabbit

• Bug Fixes
  • Corrected multiple typos, updating all instances of "wrapcast" to "warpcast" in provider names, identifiers, and UI text for improved consistency and clarity.

[coderabbitai[bot]]

Walkthrough

This change set corrects typographical errors in the naming of the "Warpcast" provider across multiple frontend and backend files. Component names, identifiers, and related strings were updated from various misspellings such as "Wrapcast" and "Wrapcaster" to the correct "Warpcast" and "Warpcaster" forms. No logic or structural changes were made.

Changes

File(s)	Change Summary
.../providers/show.all.providers.tsx .../web3/web3.list.tsx	Updated provider identifier and component references from 'wrapcast'/'Wrapcaster' to 'warpcast'/'Warpcaster'.
.../providers/warpcast/warpcast.provider.tsx	Renamed component and export from WrapcastProvider to WarpcastProvider.
.../web3/providers/nostr.provider.tsx .../web3/providers/warpcaster.provider.tsx	Renamed components and UI text from WrapcasterProvider/Add Wrapcast to WarpcasterProvider/Add Warpcast.
libraries/nestjs-libraries/src/integrations/social/farcaster.provider.ts	Changed identifier property from 'wrapcast' to 'warpcast' in FarcasterProvider class.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Frontend
    participant WarpcastProvider
    participant Backend (FarcasterProvider)

    User->>Frontend: Selects Warpcast integration
    Frontend->>WarpcastProvider: Initialize provider
    WarpcastProvider->>Backend (FarcasterProvider): Communicate using identifier 'warpcast'
    Backend (FarcasterProvider)-->>WarpcastProvider: Responds to integration request
    WarpcastProvider-->>Frontend: Updates UI/status
    Frontend-->>User: Shows Warpcast integration result

Possibly related PRs

• gitroomhq/postiz-app#562: Introduced the initial addition of the Warpcast provider and Web3 integration features, which are directly impacted by the naming corrections in this PR.

Poem

In the garden of code where typos may sprout,
The Warpcast rabbit hops and sniffs them out.
No more "Wrapcast" confusion in sight—
Just "Warpcast" shining, spelled exactly right.
With a twitch of the nose and a flick of the ear,
Our provider names are now crystal clear!
🐇✨

[!WARNING] There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

apps/frontend/src/components/launches/providers/show.all.providers.tsx

Oops! Something went wrong! :(

ESLint: 8.57.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@eslint/eslintrc' imported from /eslint.config.mjs at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9) at packageResolve (node:internal/modules/esm/resolve:767:81) at moduleResolve (node:internal/modules/esm/resolve:853:18) at defaultResolve (node:internal/modules/esm/resolve:983:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:799:12) at #cachedDefaultResolve (node:internal/modules/esm/loader:723:25) at ModuleLoader.resolve (node:internal/modules/esm/loader:706:38) at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:307:38) at #link (node:internal/modules/esm/module_job:170:49)

apps/frontend/src/components/launches/providers/warpcast/warpcast.provider.tsx

Oops! Something went wrong! :(

ESLint: 8.57.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@eslint/eslintrc' imported from /eslint.config.mjs at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9) at packageResolve (node:internal/modules/esm/resolve:767:81) at moduleResolve (node:internal/modules/esm/resolve:853:18) at defaultResolve (node:internal/modules/esm/resolve:983:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:799:12) at #cachedDefaultResolve (node:internal/modules/esm/loader:723:25) at ModuleLoader.resolve (node:internal/modules/esm/loader:706:38) at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:307:38) at #link (node:internal/modules/esm/module_job:170:49)

apps/frontend/src/components/launches/web3/providers/nostr.provider.tsx

Oops! Something went wrong! :(

ESLint: 8.57.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@eslint/eslintrc' imported from /eslint.config.mjs at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9) at packageResolve (node:internal/modules/esm/resolve:767:81) at moduleResolve (node:internal/modules/esm/resolve:853:18) at defaultResolve (node:internal/modules/esm/resolve:983:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:799:12) at #cachedDefaultResolve (node:internal/modules/esm/loader:723:25) at ModuleLoader.resolve (node:internal/modules/esm/loader:706:38) at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:307:38) at #link (node:internal/modules/esm/module_job:170:49)

• 3 others

✨ Finishing Touches

• [ ] 📝 Generate Docstrings

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this 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.

[vercel[bot]]

@dominictayloruk is attempting to deploy a commit to the Listinai Team on Vercel.

A member of the Team first needs to authorize it.

[nevo-david]

Thank you, but you cannot change the provider identifier as people use it in production. Please only change the label and the logo.

[dominictayloruk]

Thank you, but you cannot change the provider identifier as people use it in production. Please only change the label and the logo.

Surely its a typo though?

[nevo-david]

Thank you, but you cannot change the provider identifier as people use it in production. Please only change the label and the logo.

Surely its a typo though?

it is, but we can't fix it

[dominictayloruk]

Probably the better solution would be to add a fresh Farcast/Farcaster provider rather than rename the existing Warpcast/Wrapcast one, then obviously have a deprecation warning that all integrations need to be migrated to the new Farcaster provider by x.x.x version.

[nevo-david]

@dominictayloruk I think the best way is to leave the typo in the identifier since it's not visible to anybody and change the name / picture.

[nevo-david]

Closing it right now, to prevent a risk of this being merged by another mod. If you can leave the typo in the identifier and create a new pull request only with the name/logo change, it will be better! Thank you!