Provide API information to 0xAvenue

[sync-by-unito]

Tammy Yang According to the discussion today, we'll need to provide

1. API for 0xAvanue to quest Numbers backend by Order ID
2. return of Bump @capacitor/cli from 2.2.1 to 2.3.0 #1 API (Need CID & wallet address )
3. Information we need for purchase info update

不確定需要多少時間，我先設定週四 due

Ref: https://app.mural.co/t/numbersprotocol9275/m/numbersprotocol9275/1646379754948/0b16b8d2651ecc391772e46c4c70b332b16f3193?sender=u35598127f07f9403e0a66899

┆Issue is synchronized with this Asana task by Unito
┆Created By: Sherry Chung

[sync-by-unito]

➤ PJ commented:

因為我負責串接0xAvenue API所以先 join task跟進目前進度，謝謝

[sync-by-unito]

➤ Sherry Chung commented:

Tammy YangPJ 已取得 0xAvenue URL 參數，再麻煩提供 API for 0xAvenue

• URL: https://www.0xavenue.io/launch?channel=numbers&order_id=666 ( https://www.0xavenue.io/launch?channel=numbers&order_id=666 )
• Information needed for 0xAvenue

• blockchain (ethereum, solana....)
• asset url
• owner wallet address
• (optional) user name
• (optional) token name

[sync-by-unito]

➤ PJ commented:

Tammy Yang
I think the information they need is quite similar to the orderDB structure (What Ray demo yesterday), 0xAvenue can query our bubbleDB through order_id and retrieve info.(not sure with the idea)

[sync-by-unito]

➤ Sherry Chung commented:

Tammy Yang 這個我在等你回覆要提供給 0xAvenue 的 API 資訊，或請告知應該改 assign 給誰

[sync-by-unito]

➤ Tammy Yang commented:

Sherry Chung 你可以先請 PJ 提供，他上面訊息的概念很接近，我做 review 比較快

[sync-by-unito]

➤ PJ commented:

Sherry Chung 我明天會給一版spec放在這，再請 Tammy Yang review, thanks!

[sync-by-unito]

➤ PJ commented:

According to the flow here https://miro.com/app/board/o9J_knFcMnw=/?moveToWidget=3458764520664359089&cot=14 ( https://miro.com/app/board/o9J_knFcMnw=/?moveToWidget=3458764520664359089&cot=14 ) and the current OrderDB structure, I think we can simplify the flow:

Since the information 0xAvenue needs(blockchain name, asset url(cid?), owner wallet address are in OrderDB, also this network app doesn't require $NUM, I think we can skip the work for storage backend ←→ 0xAvenue here. We can leverage bubble workflow for 0xAvenue to access these information by order_id.

For example,
call type: POST
url: https://numbers-upvote.bubbleapps.io/api/1.1/wf/0xAvenue ( https://numbers-upvote.bubbleapps.io/version-test/api/1.1/wf )
test_url: https://numbers-upvote.bubbleapps.io/version-test/api/1.1/wf/0xAvenue ( https://numbers-upvote.bubbleapps.io/version-test/api/1.1/wf/0xAvenue )
(Name are subject to change)
query_params: {order_id: string}
return: {blockchain: str,
asset_cid(or asset_url): str,
owner_wallet_address: str}

For purchase info update
call type: POST
url: https://numbers-upvote.bubbleapps.io/api/1.1/wf/0xAvenue-update ( https://numbers-upvote.bubbleapps.io/version-test/api/1.1/wf )

(Name are subject to change)
body_params: info to update
return: {blockchain: str,
asset_cid(or asset_url): str,
owner_wallet_address: str,
update_info: updated info}
Sherry ChungTammy Yang

[sync-by-unito]

➤ Tammy Yang commented:

PJ we don't have those APIs yet, right?

Suggest endpoints

order-create
order-update

instead of "0xAvenue" and "0xAvenue-update" ALWAYS prevent putting user name or company name in the endpoint or anywhere.

[sync-by-unito]

➤ Tammy Yang commented:

If they have been implemented, submit a QA release and only share AFTER test passes.

[sync-by-unito]

➤ PJ commented:

Tammy Yang Yes, I haven't implemented these endpoints since the design is different from the miro flow: https://miro.com/app/board/o9J_knFcMnw=/?moveToWidget=3458764520664359089&cot=14 ( https://miro.com/app/board/o9J_knFcMnw=/?moveToWidget=3458764520664359089&cot=14 ) . If the spec proposed above works for you, I will implement 'order-create' and 'order-update' API in numbers-upvote tomorrow.

[sync-by-unito]

➤ Tammy Yang commented:

User story for Scott Yan

As a 0xAvenue developer, I need APIs and clear instructions so that I know how to create Capture App network action with Numbers together.

[sync-by-unito]

➤ Sherry Chung commented:

Scott Yan 明天這裡會有一個多餘的測試

[sync-by-unito]

➤ PJ commented:

QA Test Detail:
目前為測試API階段，測試兩隻API: order-info / order-update (目前endpoint已建好)
[order-info]
url: https://numbers-upvote.bubbleapps.io/version-avenue0x/api/1.1/wf/order-info
request body: {order_id: str}
response: {blockchain_name: str, asset_cid: str, owner_wallet_address: str}

[order-update]
url: https://numbers-upvote.bubbleapps.io/version-avenue0x/api/1.1/wf/order-update
request body:
{ network_action_cost: number(required),
cost_token_ticker: str(required),
blockchain_name: str(optional),
result_tx: str(optional),
result_url: str(optional)}

return:
{success: true/false}

TESTING DATA:
#1 : order_id: "123", 資料: blockchain_name: IOTA, asset_cid: test_asset_cid_1, owner_wallet_address: test_wallet_address_1
#2: order_id: "456", 資料: blockchain_name: IOTA, asset_cid: test_asset_cid_2, owner_wallet_address: test_wallet_address_2
#3: order_id: "789", 資料: blockchain_name: IOTA, asset_cid: test_asset_cid_3 owner_wallet_address: test_wallet_address_3

Suggest testing steps:

1. 用order-info測試是否能取到如測試資料一樣的內容
2. 用order-update測試修改測試資料的內容，並於bubble db中確認Order中對應order_id的欄位內容於預期被修改成user input

[sync-by-unito]

➤ Tammy Yang commented:

請問這個項目的進度?

[sync-by-unito]

➤ PJ commented:

Tammy Yang waiting for ‘extend network action to redirect to other side’