From 57a1fca2c0c8921cb7a4e9d38ab1355d5ff17d88 Mon Sep 17 00:00:00 2001 From: kienn6034 Date: Thu, 19 Dec 2024 00:12:48 +0700 Subject: [PATCH 1/2] docs: fix broken links --- docs/docs/04-middleware/02-callbacks/01-overview.md | 2 +- .../version-v7.8.x/04-middleware/02-callbacks/01-overview.md | 2 +- .../version-v8.5.x/04-middleware/02-callbacks/01-overview.md | 2 +- .../version-v9.0.x/04-middleware/02-callbacks/01-overview.md | 2 +- modules/apps/callbacks/README.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/docs/04-middleware/02-callbacks/01-overview.md b/docs/docs/04-middleware/02-callbacks/01-overview.md index 6dce7ed4759..16d7daa1bfb 100644 --- a/docs/docs/04-middleware/02-callbacks/01-overview.md +++ b/docs/docs/04-middleware/02-callbacks/01-overview.md @@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs. -After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs), and the Callbacks Middleware is an implementation of that ADR. +After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. ## Concepts diff --git a/docs/versioned_docs/version-v7.8.x/04-middleware/02-callbacks/01-overview.md b/docs/versioned_docs/version-v7.8.x/04-middleware/02-callbacks/01-overview.md index ca469a80e79..8c88319d909 100644 --- a/docs/versioned_docs/version-v7.8.x/04-middleware/02-callbacks/01-overview.md +++ b/docs/versioned_docs/version-v7.8.x/04-middleware/02-callbacks/01-overview.md @@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs. -After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs), and the Callbacks Middleware is an implementation of that ADR. +After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. ## Concepts diff --git a/docs/versioned_docs/version-v8.5.x/04-middleware/02-callbacks/01-overview.md b/docs/versioned_docs/version-v8.5.x/04-middleware/02-callbacks/01-overview.md index ca469a80e79..8c88319d909 100644 --- a/docs/versioned_docs/version-v8.5.x/04-middleware/02-callbacks/01-overview.md +++ b/docs/versioned_docs/version-v8.5.x/04-middleware/02-callbacks/01-overview.md @@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs. -After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs), and the Callbacks Middleware is an implementation of that ADR. +After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. ## Concepts diff --git a/docs/versioned_docs/version-v9.0.x/04-middleware/02-callbacks/01-overview.md b/docs/versioned_docs/version-v9.0.x/04-middleware/02-callbacks/01-overview.md index 6dce7ed4759..16d7daa1bfb 100644 --- a/docs/versioned_docs/version-v9.0.x/04-middleware/02-callbacks/01-overview.md +++ b/docs/versioned_docs/version-v9.0.x/04-middleware/02-callbacks/01-overview.md @@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs. -After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs), and the Callbacks Middleware is an implementation of that ADR. +After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. ## Concepts diff --git a/modules/apps/callbacks/README.md b/modules/apps/callbacks/README.md index 002fb414e8c..be2f27bc57c 100644 --- a/modules/apps/callbacks/README.md +++ b/modules/apps/callbacks/README.md @@ -6,7 +6,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs. -After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs), and the Callbacks Middleware is an implementation of that ADR. +After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. ## Version Matrix From eb44cd6c84df3d1381fa359f41b75117c2447fee Mon Sep 17 00:00:00 2001 From: kienn6034 Date: Thu, 19 Dec 2024 00:53:08 +0700 Subject: [PATCH 2/2] fix: correct readme path --- docs/docs/04-middleware/02-callbacks/01-overview.md | 2 +- .../version-v7.8.x/04-middleware/02-callbacks/01-overview.md | 2 +- .../version-v8.5.x/04-middleware/02-callbacks/01-overview.md | 2 +- .../version-v9.0.x/04-middleware/02-callbacks/01-overview.md | 2 +- modules/apps/callbacks/README.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/docs/04-middleware/02-callbacks/01-overview.md b/docs/docs/04-middleware/02-callbacks/01-overview.md index 16d7daa1bfb..6a642cdf698 100644 --- a/docs/docs/04-middleware/02-callbacks/01-overview.md +++ b/docs/docs/04-middleware/02-callbacks/01-overview.md @@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs. -After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. +After much discussion, the design was expanded to [an ADR](../../../architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. ## Concepts diff --git a/docs/versioned_docs/version-v7.8.x/04-middleware/02-callbacks/01-overview.md b/docs/versioned_docs/version-v7.8.x/04-middleware/02-callbacks/01-overview.md index 8c88319d909..2a9bdb52063 100644 --- a/docs/versioned_docs/version-v7.8.x/04-middleware/02-callbacks/01-overview.md +++ b/docs/versioned_docs/version-v7.8.x/04-middleware/02-callbacks/01-overview.md @@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs. -After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. +After much discussion, the design was expanded to [an ADR](../../../../architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. ## Concepts diff --git a/docs/versioned_docs/version-v8.5.x/04-middleware/02-callbacks/01-overview.md b/docs/versioned_docs/version-v8.5.x/04-middleware/02-callbacks/01-overview.md index 8c88319d909..2a9bdb52063 100644 --- a/docs/versioned_docs/version-v8.5.x/04-middleware/02-callbacks/01-overview.md +++ b/docs/versioned_docs/version-v8.5.x/04-middleware/02-callbacks/01-overview.md @@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs. -After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. +After much discussion, the design was expanded to [an ADR](../../../../architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. ## Concepts diff --git a/docs/versioned_docs/version-v9.0.x/04-middleware/02-callbacks/01-overview.md b/docs/versioned_docs/version-v9.0.x/04-middleware/02-callbacks/01-overview.md index 16d7daa1bfb..604028120b9 100644 --- a/docs/versioned_docs/version-v9.0.x/04-middleware/02-callbacks/01-overview.md +++ b/docs/versioned_docs/version-v9.0.x/04-middleware/02-callbacks/01-overview.md @@ -17,7 +17,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs. -After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. +After much discussion, the design was expanded to [an ADR](../../../../architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. ## Concepts diff --git a/modules/apps/callbacks/README.md b/modules/apps/callbacks/README.md index be2f27bc57c..62fd3c54805 100644 --- a/modules/apps/callbacks/README.md +++ b/modules/apps/callbacks/README.md @@ -6,7 +6,7 @@ This setup worked well for off-chain users interacting with IBC applications. Ho The Callbacks Middleware allows for this functionality by allowing the packets of the underlying IBC applications to register callbacks to secondary applications for lifecycle events. These callbacks are then executed by the Callbacks Middleware when the corresponding packet lifecycle event occurs. -After much discussion, the design was expanded to [an ADR](/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. +After much discussion, the design was expanded to [an ADR](../../../docs/architecture/adr-008-app-caller-cbs.md), and the Callbacks Middleware is an implementation of that ADR. ## Version Matrix