Skip to content

Commit 7fe083c

Browse files
committed
png for ide
1 parent b55e530 commit 7fe083c

File tree

6 files changed

+5
-8
lines changed

6 files changed

+5
-8
lines changed

docs/Tutorial.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -79,8 +79,6 @@ The system creates a JSON:API with end points for each table, providing filterin
7979

8080
The API is [**self-serve**](https://apilogicserver.github.io/Docs/API-Self-Serve/): consumers can select their own attributes and related data, eliminating reliance on custom API development. Our self-serve API meets requirements for Ad Hoc Application Integration, and Custom UI Dev.
8181

82-
<img src="https://github.com/ApiLogicServer/Docs/blob/main/docs/images/integration/api-swagger.jpeg?raw=true">
83-
8482
![api-swagger](images/integration/api-swagger.png)
8583

8684
### 2.b Admin App: Multi-Page, Multi-Table, Automatic Joins
@@ -182,7 +180,7 @@ To see customized Admin app in action, with the restarted server:
182180

183181
One customization has been to hide several Order fields (search `ui/admin/admin.yml` for `show_when: isInserting == false`). This makes it convenient to use the Admin App to enter an Order and OrderDetails:
184182

185-
<img src="https://github.com/ApiLogicServer/Docs/blob/main/docs/images/integration/order-entry-ui.jpg?raw=true">
183+
![order-entry-ui](images/integration/order-entry-ui.png)
186184

187185
&nbsp;
188186

@@ -205,7 +203,7 @@ Rules are declared in Python, simplified with IDE code completion. The `add-cus
205203

206204
Observe rules can be debugged using standard logging and the debugger:
207205

208-
<img src="https://github.com/ApiLogicServer/Docs/blob/main/docs/images/integration/logic-chaining.jpeg?raw=true">
206+
![logic-chaining](images/integration/logic-chaining.png)
209207

210208
&nbsp;
211209

@@ -257,7 +255,7 @@ To see security in action:
257255

258256
Declarative row-level security ensures that users see only the rows authorized for their roles. Observe you now see only customer ALFKI, per the security declared below. Note the console log at the bottom shows how the filter worked.
259257

260-
<img src="https://github.com/ApiLogicServer/Docs/blob/main/docs/images/integration/security-filters.jpg?raw=true">
258+
![security-filter](images/integration/security-filters.png)
261259

262260
&nbsp;
263261

@@ -292,7 +290,7 @@ The main task here is to ***map*** a B2B payload onto our logic-enabled SQLAlche
292290
* Use the `OrderB2B` class to transform a api request data to SQLAlchemy rows (`dict_to_row`)
293291
* The automatic commit initiates the same shared logic described above to check credit and reorder products
294292

295-
![dict to row](https://github.com/ApiLogicServer/Docs/blob/main/docs/images/integration/dict-to-row.jpg?raw=true)
293+
![dict-to-row](images/integration/dict-to-row.png)
296294

297295

298296
&nbsp;
@@ -319,8 +317,7 @@ Just as you can customize apis, you can complement rule-based logic using Python
319317

320318
3. `send_order_to_shipping` uses the `OrderShipping` class, which maps our SQLAlchemy order row to a dict (`row_to_dict`).
321319

322-
![send order to shipping](https://github.com/ApiLogicServer/Docs/blob/main/docs/images/integration/order-to-shipping.jpg?raw=true)
323-
320+
![order-to-shipping](images/integration/order-to-shipping.png)
324321

325322
&nbsp;
326323
> **Key Takeway - Extensible Rules, Kafka Message Produced**<br>Rule-based logic is extensible with Python, here producing a Kafka message with 20 lines of code.
1.96 MB
Loading
2.25 MB
Loading
539 KB
Loading
1.99 MB
Loading
2.26 MB
Loading

0 commit comments

Comments
 (0)