Adding backlinks

Author: oswaldsql

docs/ADR/CreatingMocks.md

@@ -20,3 +20,7 @@ Mocks will be created using a mock factory. The mock factory will provide a cent
 
 - **Complexity**: Introduces an additional layer of abstraction, which may add some complexity to the framework.
 - **Maintenance**: Requires ongoing maintenance to ensure the mock factory remains up-to-date with any changes to the framework.
+
+---
+
+More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.

docs/ADR/DoWeNeedANewMockingFramework.md

@@ -22,3 +22,7 @@ We will develop a new mocking framework, MiniMock, that focuses on providing a m
 - **Feature Limitations**: The framework may lack some advanced features found in more comprehensive mocking frameworks.
 - **Development Effort**: Additional effort will be required to develop and maintain the new framework.
 - **Adoption**: Convincing developers to switch to a new framework may be challenging, especially if they are accustomed to existing solutions.
+
+---
+
+More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.

docs/ADR/DocumentationAndExamples.md

@@ -39,3 +39,7 @@ Accepted
 - **Basic Mocking**: Simple example showing how to create and use a mock.
 - **Advanced Mocking**: Examples of more complex scenarios, such as mocking protected methods and handling asynchronous methods.
 - **Integration**: Examples showing how to integrate the framework with other tools and libraries.
+
+---
+
+More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.

docs/ADR/HowStrictShouldMiniMockBe.md

@@ -20,3 +20,7 @@ The framework will be strict, throwing exceptions when a member that is not mock
 
 - **Strictness**: The strict approach may require more effort to set up mocks, as all interactions must be explicitly defined.
 - **Event Handling**: Special handling for events may introduce some complexity in the framework.
+
+---
+
+More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.

docs/ADR/LoggingAndDebugging.md

@@ -30,25 +30,6 @@ Accepted
 1. **Logging**: Plan and design the logging mechanism to capture mock setup events and calls to mocks.
 2. **DebuggerStepThrough**: Apply the `DebuggerStepThrough` attribute to relevant methods and classes to improve the debugging experience.
 
-## Example
-
-```csharp
-[System.Diagnostics.DebuggerStepThrough]
-public void SetupMock()
-{
-    // Setup mock logic
-    Log("Mock setup completed.");
-}
-
-[System.Diagnostics.DebuggerStepThrough]
-public void CallMock()
-{
-    // Call mock logic
-    Log("Mock method called.");
-}
-
-private void Log(string message)
-{
-    // Placeholder for logging implementation
-    Console.WriteLine(message);
-}
+---
+
+More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.

docs/ADR/MatchingTargetApi.md

@@ -20,3 +20,7 @@ Accepted
 ### Negative:
 - Limited flexibility in extending the mock API for advanced testing scenarios.
 - May require more effort to implement certain mocking features without additional methods.
+
+---
+
+More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.

docs/ADR/NoBuiltInAssertionFeature.md

@@ -20,3 +20,7 @@ We will not include a built-in assertion feature in our mocking framework. Inste
 
 - **Learning Curve**: Users may need to learn and integrate a separate assertion framework if they are not already familiar with one.
 - **Dependency Management**: Users will need to manage additional dependencies for their chosen assertion framework.
+
+---
+
+More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.

docs/ADR/NoDependencies.md

@@ -22,3 +22,7 @@ We will not include any dependencies on shared libraries in our project. Instead
 - **Development Effort**: May require additional effort to implement functionality that would otherwise be provided by shared libraries.
 - **Code Duplication**: Potential for code duplication if similar functionality is needed across multiple projects.
 - **Maintenance**: Increased maintenance burden as all functionality must be maintained within the project.
+
+---
+
+More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.

docs/ADR/SupportSkippingArguments.md

@@ -19,3 +19,7 @@ We will allow the skipping of arguments when setting up mocks for methods. This
 - **Clarity**: May reduce the clarity of tests if arguments are skipped without proper documentation.
 - **Consistency**: Could lead to inconsistent mock setups across the codebase if not used judiciously.
 - **Error Potential**: Increases the risk of errors if skipped arguments are assumed incorrectly.~~~~
+
+---
+
+More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.

docs/ADR/feature/SupportForClassesAndInterfaces.md

@@ -21,3 +21,7 @@ The MiniMock framework will primarily focus on supporting interfaces but will al
 - **Complexity**: Adding support for classes may introduce additional complexity in the framework.
 - **Maintenance**: Requires ongoing maintenance to ensure both interfaces and classes are supported effectively.
 f mocking scenarios.
+
+---
+
+More ADRs can be found in the [docs/ADR](../README.md) directory.