Skip to content

Commit 97e7195

Browse files
fix: update links for Plugins and IWYU standard in C++ API Reference and Modules documentation
1 parent a0419bc commit 97e7195

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

docs/engine/cpp-api-reference/cpp-api-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Welcome to the Graphical Playground C++ API Reference! This is a reference manua
1616

1717
Graphical Playground's systems and features are packaged in two ways:
1818
- [Modules](../programming-with-cpp/engine-architecture/modules.md): The basic building block of Graphical Playground's software and architecture.
19-
- [Plugins](): Collections of modules and assets that you can enable or disable within the Editor on a per-project basis.
19+
- [Plugins](#): Collections of modules and assets that you can enable or disable within the Editor on a per-project basis.
2020

2121
Explore all of Graphical Playground's modules, plugins, and their members here, organized hierarchically. You can use the search bar to find a known term, such as a class or function name.
2222

docs/engine/programming-with-cpp/engine-architecture/modules.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ GP Engine modules are not related to C++ 20 modules.
3030
Organizing your project with modules provides the following benefits:
3131
- Modules enforce good code separation, providing a means to encapsulate functionality and hide internal parts of the code.
3232
- Modules are compiled as separate compilation units. This means only modules that have changed will need to compile, and build times for larger projects will be significantly faster.
33-
- Modules are linked together in a dependency graph and limit header includes to code that is actually used, per the [Include What You Use (IWYU)]() standard. This means modules that are not used in your project will be safely excluded from compilation.
33+
- Modules are linked together in a dependency graph and limit header includes to code that is actually used, per the [Include What You Use (IWYU)](#) standard. This means modules that are not used in your project will be safely excluded from compilation.
3434
- You can control when specific modules are loaded and unloaded at runtime. This provides a way to optimize the performance of your project by managing which systems are available and active.
3535
- Modules can be included or excluded from your project based on certain conditions, such as which platform the project is being compiled for.
3636

0 commit comments

Comments
 (0)