You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Rename bitauthUri to getBitauthUri and update docs for it
- Move around some utils
- Add getVmResourceUsage to release notes and docs
- Update docs for MockNetworkProvider default changes
Copy file name to clipboardExpand all lines: website/docs/guides/debugging.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,10 +42,10 @@ To help with debugging you can add `console.log` statements to your CashScript c
42
42
43
43
Whenever a transaction fails, there will be a link in the console to open your smart contract transaction in the BitAuth IDE. This will allow you to inspect the transaction in detail, and see exactly why the transaction failed. In the BitAuth IDE you will see the raw BCH Script mapping to each line in your CashScript contract. Find the failing line and investigate the failing OpCode. You can break up the failing line, one opcode at a time, to see how the stack evolves and ends with your `require` failure.
44
44
45
-
It's also possible to export the transaction for step-by-step debugging in the BitAuth IDE without failure. To do so, you can call the `bitauthUri()` function on the transaction. This will return a URI that can be opened in the BitAuth IDE.
45
+
It's also possible to export the transaction for step-by-step debugging in the BitAuth IDE without failure. To do so, you can call the `getBitauthUri()` function on the transaction. This will return a URI that can be opened in the BitAuth IDE.
46
46
47
47
```ts
48
-
const uri =awaittransactionBuilder.bitauthUri();
48
+
const uri =awaittransactionBuilder.getBitauthUri();
0 commit comments