Skip to content

Conversation

@saminacodes
Copy link
Member

@saminacodes saminacodes commented Jul 1, 2025

CORE-0000

added article on deletng engine cloud


PR-Codex overview

This PR adds a new section to the page.mdx file, providing guidance on how to delete Transactions Cloud. It enhances the documentation by offering clear instructions for users.

Detailed summary

  • Added a new Details section with the summary "How do I delete Transactions Cloud?"
  • Included instructions on stopping requests to Transactions Cloud and removing associated code.
  • Mentioned the option to delete the project if no other features are used.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

  • Documentation
    • Added a new collapsible section to the troubleshooting guide with instructions on deleting Transactions Cloud and related project removal steps.

Signed-off-by: samina <[email protected]>
@saminacodes saminacodes requested review from a team as code owners July 1, 2025 20:10
@changeset-bot
Copy link

changeset-bot bot commented Jul 1, 2025

⚠️ No Changeset found

Latest commit: c5ff6bd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Jul 1, 2025

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

Name Status Preview Comments Updated (UTC)
docs-v2 ❌ Failed (Inspect) Jul 1, 2025 9:01pm
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
nebula ⬜️ Skipped (Inspect) Jul 1, 2025 9:01pm
thirdweb_playground ⬜️ Skipped (Inspect) Jul 1, 2025 9:01pm
thirdweb-www ⬜️ Skipped (Inspect) Jul 1, 2025 9:01pm
wallet-ui ⬜️ Skipped (Inspect) Jul 1, 2025 9:01pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 1, 2025

Walkthrough

A new collapsible section was added to the troubleshooting guide, providing instructions for deleting Transactions Cloud. The update explains how to remove associated code and when to delete the entire project. No existing content or logic was changed.

Changes

File(s) Change Summary
apps/portal/src/app/engine/v3/troubleshoot/page.mdx Added a collapsible section detailing how to delete Transactions Cloud and related instructions.

Sequence Diagram(s)

No sequence diagram generated as the change is documentation-only.

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • CORE-0000: Entity not found: Issue - Could not find referenced Issue.

🪧 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.

@graphite-app
Copy link
Contributor

graphite-app bot commented Jul 1, 2025

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

@github-actions github-actions bot added the Portal Involves changes to the Portal (docs) codebase. label Jul 1, 2025
@codecov
Copy link

codecov bot commented Jul 1, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.92%. Comparing base (c356813) to head (c5ff6bd).
Report is 23 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7496   +/-   ##
=======================================
  Coverage   51.92%   51.92%           
=======================================
  Files         949      949           
  Lines       64148    64148           
  Branches     4229     4229           
=======================================
  Hits        33311    33311           
  Misses      30731    30731           
  Partials      106      106           
Flag Coverage Δ
packages 51.92% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 030c522 and c5ff6bd.

📒 Files selected for processing (1)
  • apps/portal/src/app/engine/v3/troubleshoot/page.mdx (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-06-30T10:25:29.488Z
Learning: Surface breaking changes prominently in PR descriptions
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Unit Tests
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: Size
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Lint Packages
  • GitHub Check: Build Packages
  • GitHub Check: Analyze (javascript)

Comment on lines +12 to +16
<Details summary="How do I delete Transactions Cloud?">

To delete or stop sending requests on Transactions Cloud, you may stop sending requests through your codebase and remove associated code. If you don't want Transactions Cloud and are not using any other features within the same project, you may delete the associated project as well.

</Details>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Clarify product naming & give concrete deletion steps

The header refers to “Transactions Cloud”, yet the PR description says the doc is for deleting Engine Cloud. If the service was renamed, we risk confusing users.
Additionally, simply telling users to “remove associated code” lacks actionable detail (e.g., which SDK calls / dashboard toggles to disable). A quick bullet-list or link to the “Delete project” UI would make the guidance far more useful.

Example patch:

-<Details summary="How do I delete Transactions Cloud?">
-
-To delete or stop sending requests on Transactions Cloud, you may stop sending requests through your codebase and remove associated code. If you don't want Transactions Cloud and are not using any other features within the same project, you may delete the associated project as well. 
-
-</Details>
+<Details summary="How do I delete Engine Cloud?">
+
+If you no longer need Engine Cloud:
+
+1. **Remove SDK calls** – delete any `engine.send(...)` or `thirdwebEngine.*` invocations in your codebase.  
+2. **Disable the service** – in the dashboard, go to **Project Settings → Services → Engine Cloud** and toggle it off.  
+3. **Delete the project (optional)** – if the project is unused, scroll to **Danger Zone → Delete Project**.
+
+</Details>

This resolves the naming discrepancy and provides step-by-step instructions.

Ensure the product name in the summary matches the branding used across the docs/repo. If it really is “Transactions Cloud”, adjust references elsewhere accordingly.


🏁 Script executed:

#!/bin/bash
# Search for occurrences of "Transactions Cloud" versus "Engine Cloud" across the repository
rg "Transactions Cloud" -n
rg "Engine Cloud" -n

Length of output: 4986


Maintain “Transactions Cloud” naming & add actionable deletion steps

The header should remain “Transactions Cloud” (v3 docs consistently use this term). Expand the details to give users concrete, step‐by‐step instructions.

apps/portal/src/app/engine/v3/troubleshoot/page.mdx

-<Details summary="How do I delete Transactions Cloud?">
-
-To delete or stop sending requests on Transactions Cloud, you may stop sending requests through your codebase and remove associated code. If you don't want Transactions Cloud and are not using any other features within the same project, you may delete the associated project as well. 
-
-</Details>
+<Details summary="How do I delete Transactions Cloud?">
+
+If you no longer need Transactions Cloud:
+
+1. **Remove SDK calls** – delete any `transactions.send(...)` or `thirdweb.transactions.*` invocations in your code.
+2. **Disable the service** – in the dashboard, go to **Project Settings → Services → Transactions Cloud** and toggle it off.
+3. **Delete the project (optional)** – if the project is unused, scroll to **Danger Zone → Delete Project**.
+
+</Details>
  • Keeps naming aligned with v3 docs
  • Provides clear, actionable steps for both code and dashboard cleanup
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<Details summary="How do I delete Transactions Cloud?">
To delete or stop sending requests on Transactions Cloud, you may stop sending requests through your codebase and remove associated code. If you don't want Transactions Cloud and are not using any other features within the same project, you may delete the associated project as well.
</Details>
<Details summary="How do I delete Transactions Cloud?">
If you no longer need Transactions Cloud:
1. **Remove SDK calls** – delete any `transactions.send(...)` or `thirdweb.transactions.*` invocations in your code.
2. **Disable the service** – in the dashboard, go to **Project Settings → Services → Transactions Cloud** and toggle it off.
3. **Delete the project (optional)** – if the project is unused, scroll to **Danger Zone → Delete Project**.
</Details>
🤖 Prompt for AI Agents
In apps/portal/src/app/engine/v3/troubleshoot/page.mdx around lines 12 to 16,
keep the header as "Transactions Cloud" to maintain naming consistency with v3
docs. Expand the content inside the Details tag to include clear, step-by-step
instructions for users on how to delete or stop using Transactions Cloud,
covering both codebase changes (like stopping requests and removing related
code) and dashboard/project cleanup actions. Make sure the instructions are
actionable and easy to follow.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 1, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 63.11 KB (0%) 1.3 s (0%) 689 ms (+112.3% 🔺) 2 s
thirdweb (cjs) 352.76 KB (0%) 7.1 s (0%) 2.5 s (+4.63% 🔺) 9.6 s
thirdweb (minimal + tree-shaking) 5.72 KB (0%) 115 ms (0%) 297 ms (+1494.27% 🔺) 411 ms
thirdweb/chains (tree-shaking) 530 B (0%) 11 ms (0%) 129 ms (+1142.53% 🔺) 139 ms
thirdweb/react (minimal + tree-shaking) 19.59 KB (0%) 392 ms (0%) 312 ms (+474.86% 🔺) 704 ms

</Details>
</Details>

<Details summary="How do I delete Transactions Cloud?">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is more of a FAQ no?

@saminacodes saminacodes closed this Jul 3, 2025
@saminacodes saminacodes deleted the saminacodes-patch-1 branch July 3, 2025 00:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Portal Involves changes to the Portal (docs) codebase.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants