Skip to content

Commit

Permalink
📝 (doc): Add missing _meta.js file
Browse files Browse the repository at this point in the history
  • Loading branch information
valpinkman committed Jan 27, 2025
1 parent c433523 commit 1a34fed
Show file tree
Hide file tree
Showing 7 changed files with 16 additions and 13 deletions.
14 changes: 5 additions & 9 deletions apps/docs/pages/docs/explanations/transports/transports.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,18 +5,14 @@ Depending on the environment and usecase, you can choose the transport that best

## Available transports

| Transport | Description |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------- |
| [WebHid](https://www.npmjs.com/package/@ledgerhq/device-transport-kit-web-hid) | The WebHID transport is a transport that uses the WebHID API (usb) to communicate with a Ledger device. |
| [WebBle](https://www.npmjs.com/package/@ledgerhq/device-transport-kit-web-ble) | The WebBLE transport is a transport that uses the WebBLE API (bluetooth) to communicate with a Ledger device. |

### WebBLE

The WebBLE transport is a transport that uses the WebBLE API (bluetooth) to communicate with a Ledger device.
| Transport | Description |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------ |
| [WebHid](https://www.npmjs.com/package/@ledgerhq/device-transport-kit-web-hid) | The WebHID transport uses the Web HID API (usb) to communicate with a Ledger device. |
| [WebBle](https://www.npmjs.com/package/@ledgerhq/device-transport-kit-web-ble) | The WebBLE transport uses the Web BLE API (bluetooth) to communicate with a Ledger device. |

## How to use a transport

Transports are injected in the DeviceManagementKitBuilder before building the DeviceManagementKit instance.
Transports are injected in the DeviceManagementKitBuilder before building the Device Management Kit instance.
This is done by calling the `addTransport` method on the builder.
You can inject the transport in two different ways:

Expand Down
4 changes: 4 additions & 0 deletions apps/docs/pages/docs/migrations/_meta.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
export default {
dmk: "Device Management Kit",
signers: "Device Signer Kits",
};
2 changes: 1 addition & 1 deletion apps/docs/pages/docs/migrations/dmk/_meta.js
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
export default {
"05_to_06": "DMK: Migrate from v0.5.0 to 0.6.0",
"05_to_06": "v0.5.0 -> 0.6.0",
};
3 changes: 0 additions & 3 deletions apps/docs/pages/docs/migrations/signer-eth/_meta.js

This file was deleted.

3 changes: 3 additions & 0 deletions apps/docs/pages/docs/migrations/signers/_meta.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
export default {
eth: "Ethereum",
};
3 changes: 3 additions & 0 deletions apps/docs/pages/docs/migrations/signers/eth/_meta.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
export default {
"1_1_0_to_1_2_0": "v1.1.0 -> 1.2.0",
};

0 comments on commit 1a34fed

Please sign in to comment.