From b2bfac86f14097e7cef92e3abab8345f3be29fc7 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Mon, 6 May 2019 13:08:23 -0700 Subject: [PATCH] Use filter for interactive tutorial steps --- assets/css/devportal.css | 2 +- ...onitor-incoming-payments-with-websocket.md | 60 +++--- .../use-simple-xrp-payments/send-xrp.md | 186 +++++------------- dactyl-config.yml | 4 + tool/filter_interactive_steps.py | 80 ++++++++ 5 files changed, 165 insertions(+), 167 deletions(-) create mode 100644 tool/filter_interactive_steps.py diff --git a/assets/css/devportal.css b/assets/css/devportal.css index 07e4ca8f79..4a2931438e 100644 --- a/assets/css/devportal.css +++ b/assets/css/devportal.css @@ -1009,7 +1009,7 @@ a.current { margin: 5px; } -.interactive-block-inner > button { +.interactive-block-ui > button { margin: 10px 0; } diff --git a/content/tutorials/use-simple-xrp-payments/monitor-incoming-payments-with-websocket.md b/content/tutorials/use-simple-xrp-payments/monitor-incoming-payments-with-websocket.md index c472647d67..bff182ec98 100644 --- a/content/tutorials/use-simple-xrp-payments/monitor-incoming-payments-with-websocket.md +++ b/content/tutorials/use-simple-xrp-payments/monitor-incoming-payments-with-websocket.md @@ -57,37 +57,31 @@ const socket = new WebSocket('ws://localhost:6006') Example: -
-
-
- -
- -
- Connection status: - Not connected - -
Console:
-
(Log is empty)
-
-
-
+{{ start_step("Connect") }} + +Connection status: +Not connected + +
Console:
+
(Log is empty)
+{{ end_step() }} + @@ -99,10 +93,14 @@ Since WebSocket connections can have several messages going each way and there i - For any message that is a direct response to a request from the client side, the `type` is the string `response`. In this case, the server also provides an `id` field that matches the `id` provided in the request this is a response for. (This is important because responses may arrive out of order.) - For follow-up messages from [subscriptions](subscribe.html), the `type` indicates the type of follow-up message it is, such as the notification of an new transaction, ledger, or validation; or a follow-up to an ongoing [pathfinding request](path_find.html). Your client only receives these messages if it subscribes to them. +{{ start_step("Handle Incoming Messages") }} +
Handle Incoming Placeholder
+{{ end_step() }} + ## Footnotes -1. In practice, when calling an HTTP-based API multiple times, the client and server may reuse the same connection for several requests and responses. This practice is called [HTTP persistent connection, or keep-alive](https://en.wikipedia.org/wiki/HTTP_persistent_connection). From a development standpoint, the code to use an HTTP-based API is the same regardless of whether the underlying connection is new or reused. +[1.](#from-footnote-1) In practice, when calling an HTTP-based API multiple times, the client and server may reuse the same connection for several requests and responses. This practice is called [HTTP persistent connection, or keep-alive](https://en.wikipedia.org/wiki/HTTP_persistent_connection). From a development standpoint, the code to use an HTTP-based API is the same regardless of whether the underlying connection is new or reused. diff --git a/content/tutorials/use-simple-xrp-payments/send-xrp.md b/content/tutorials/use-simple-xrp-payments/send-xrp.md index 23b7a2d1e4..b38985bfc8 100644 --- a/content/tutorials/use-simple-xrp-payments/send-xrp.md +++ b/content/tutorials/use-simple-xrp-payments/send-xrp.md @@ -12,27 +12,15 @@ This tutorial explains how to send a simple XRP Payment using RippleAPI for Java - To send transactions in the XRP Ledger, you first need an address and secret key, and some XRP. You can get an address in the XRP Test Net with a supply of Test Net XRP using the following interface: -
-
-
- -
- - -
-
-
-
-
-
+{{ start_step("Generate") }} + + +
+
+
+
+{{ end_step() }} +