Link CommandArguments references to commandarguments.md

CommandAPI · DerEchtePilz · Jul 12, 2023 · Jun 8, 2023 · Jun 8, 2023 · Jun 8, 2023
commit 3af41ab3b03f02f7888658a4f3d9e3764da6630a
diff --git a/docssrc/src/argument_entities.md b/docssrc/src/argument_entities.md
@@ -13,7 +13,7 @@ There are four `EntitySelectorArgument` subclasses that determine what type of d
 - `EntitySelectorArgument.OnePlayer` - A single player, which returns a `Player` object.
 - `EntitySelectorArgument.ManyPlayers` - A collection of
8000
 players, which returns a `Collection<Player>` object.
 
-The return type is the type to be cast when retrieved from the `CommandArguments args` in the command declaration.
+The return type is the type to be cast when retrieved from the [`CommandArguments args`](./commandarguments.md) in the command declaration.
 
 <div class="example">
 

diff --git a/docssrc/src/argument_literal.md b/docssrc/src/argument_literal.md
@@ -30,7 +30,7 @@ There is a simpler alternative to the `LiteralArgument` class! Instead of having
 
 ## Literal arguments vs regular arguments
 
-Unlike regular arguments that are shown in this chapter, the literal argument is _technically_ not an argument. Due to this fact, literal arguments are [unlisted](./listed.md) by default. In other words, **the literal argument is not present in the `CommandArguments args` for the command declaration.**
+Unlike regular arguments that are shown in this chapter, the literal argument is _technically_ not an argument. Due to this fact, literal arguments are [unlisted](./listed.md) by default. In other words, **the literal argument is not present in the [`CommandArguments args`](./commandarguments.md) for the command declaration.**
 
 <div class="example">
 

diff --git a/docssrc/src/argument_multiliteral.md b/docssrc/src/argument_multiliteral.md
@@ -1,8 +1,8 @@
 # Multi literal arguments
 
-So far, we've described normal arguments and literal arguments. We've described the nuances with literal arguments and how they're not really "arguments", so they don't appear in the `CommandArguments args` for commands.
+So far, we've described normal arguments and literal arguments. We've described the nuances with literal arguments and how they're not really "arguments", so they don't appear in the [`CommandArguments args`](./commandarguments.md) for commands.
 
-Now forget all of that. Multi literal arguments are the same as literal arguments but they _do_ appear in the `CommandArguments args` for commands (i.e. they are [listed](./listed.md)). Multi literal arguments are just a way better alternative to literal arguments. The multi literal argument constructor allows you to provide a `String nodeName` and a `String... literals` of possible values which you can use for your command declaration.
+Now forget all of that. Multi literal arguments are the same as literal arguments but they _do_ appear in the [`CommandArguments args`](./commandarguments.md) for commands (i.e. they are [listed](./listed.md)). Multi literal arguments are just a way better alternative to literal arguments. The multi literal argument constructor allows you to provide a `String nodeName` and a `String... literals` of possible values which you can use for your command declaration.
 
 The multi literal argument has all of the same benefits of a regular literal argument - they are hardcoded options that the user must enter - they don't allow other values.
 

diff --git a/docssrc/src/arguments.md b/docssrc/src/arguments.md
@@ -75,7 +75,7 @@ The CommandAPI is very flexible when it comes to registering arguments, and lets
 
 ## Argument Casting
 
-To access arguments, they have to be casted to the type that the argument represents. The order of the arguments in the `CommandArguments args` is the same as the order in which the arguments were declared.
+To access arguments, they have to be casted to the type that the argument represents. The order of the arguments in the [`CommandArguments args`](./commandarguments.md) is the same as the order in which the arguments were declared.
 
 <div class="multi-pre">
 
@@ -133,7 +133,7 @@ The type to cast each argument (declared in the `dev.jorel.commandapi.arguments`
 |                                    [`LocationArgument`](./argument_locations.md#location-3d-space) | `org.bukkit.Location`                                                                                                                                                                                                                               |
 |                                     [`LongArgument`](./argument_primitives.md#numerical-arguments) | `long`                                                                                                                                                                                                                                              |
 |                                                     [`LootTableArgument`](./argument_loottable.md) | `org.bukkit.loot.LootTable`                                                                                                                                                                                                                         |
- |                                                               [`MapArgument`](./argument_map.md) | `java.util.LinkedhashMap`                                                                                                                                                                                                                            |
+ |                                                               [`MapArgument`](./argument_map.md) | `java.util.LinkedHashMap`                                                                                                                                                                                                                           |
 |                                            [`MathOperationArgument`](./argument_mathoperation.md) | `dev.jorel.commandapi.wrappers.MathOperation`                                                                                                                                                                                                       |
 |                                                       [`MultiLiteralArgument`](./argument_multiliteral.md) | `String`                                                                                                                                                                                                                                            |
 |                                                  [`NamespacedKeyArgument`](./argument_namespacedkey.md) | `org.bukkit.NamespacedKey`                                                                                                                                                                                                                          |

diff --git a/docssrc/src/listed.md b/docssrc/src/listed.md
@@ -1,8 +1,8 @@
 # Listed arguments
 
-Arguments have a setting which determine whether or not they are present in the `CommandArguments args` that is populated when executing a command.
+Arguments have a setting which determine whether or not they are present in the [`CommandArguments args`](./commandarguments.md) that is populated when executing a command.
 
-By default, the `LiteralArgument` has this setting set to `false`, hence the literal values are _not_ present in the `CommandArguments args`.
+By default, the `LiteralArgument` has this setting set to `false`, hence the literal values are _not_ present in the [`CommandArguments args`](commandarguments.md).
 
 This flag is set using the following function:
 
@@ -20,7 +20,7 @@ Say we have the following command:
 /mycommand <player> <value> <message>
 ```
 
-Let's also say that in our implementation of this command, we don't actually perform any processing for `<value>`. Hence, listing it in the `CommandArguments args` is unnecessary.
+Let's also say that in our implementation of this command, we don't actually perform any processing for `<value>`. Hence, listing it in the [`CommandArguments args`](./commandarguments.md) is unnecessary.
 
 <div class="multi-pre">
 
@@ -34,6 +34,6 @@ Let's also say that in our implementation of this command, we don't actually per
 
 </div>
 
-In this scenario, the argument `<value>` is not present in the `CommandArguments args` for the executor.
+In this scenario, the argument `<value>` is not present in the [`CommandArguments args`](./commandarguments.md) for the executor.
 
 </div>
diff --git a/docssrc/src/normalexecutors.md b/docssrc/src/normalexecutors.md
@@ -1,6 +1,6 @@
 # Normal command executors
 
-Command executors are of the following format, where `sender` is a [`CommandSender`](https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/command/CommandSender.html), and `args` is a `CommandArguments` object, which represents arguments which are parsed by the CommandAPI.
+Command executors are of the following format, where `sender` is a [`CommandSender`](https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/command/CommandSender.html), and `args` is a [`CommandArguments`](./commandarguments.md) object, which represents arguments which are parsed by the CommandAPI.
 
 ```java
 new CommandAPICommand("...")

diff --git a/docssrc/src/optional_arguments.md b/docssrc/src/optional_arguments.md
@@ -78,7 +78,7 @@ However, calling `withOptionalArguments` is safer because it makes sure that the
 
 ## Avoiding null values
 
-Previously, we've looked at how to handle null values. To make all of this easier, the CommandAPI implements multiple `getOptional()` methods for `CommandArguments`:
+Previously, we've looked at how to handle null values. To make all of this easier, the CommandAPI implements multiple `getOptional()` methods for [`CommandArguments`](./commandarguments.md):
 
 <div class="warning">
 

diff --git a/docssrc/src/stringargumentsuggestions.md b/docssrc/src/stringargumentsuggestions.md
@@ -104,7 +104,7 @@ This won't work, because we make use of a redirect:
 
 \\(\texttt{/execute run} \xrightarrow{redirect} \texttt{mycommand arg1 arg2 arg3}\\)
 
-It is not possible to access the `CommandArguments` of previously declared arguments. **If a command occurs via a redirect, the `CommandArguments` of previously declared arguments will be null**.
+It is not possible to access the [`CommandArguments`](./commandarguments.md) of previously declared arguments. **If a command occurs via a redirect, the [`CommandArguments`](./commandarguments.md) of previously declared arguments will be null**.
 
 </div>
 

diff --git a/docssrc/src/upgrading.md b/docssrc/src/upgrading.md
@@ -28,7 +28,7 @@ withArguments(new MultiLiteralArgument("gamemodes", "survival", "creative", "adv
 
 ### MultiLiteralArgument and LiteralArgument changes
 
-In previous versions, the ability has been introduced to access arguments by their node names. However, while this was possible for every other argument, it wasn't possible for `MultiLiteralArgument`s. This was now changed because the values from the `MultiLiteralArgument` are included in the `CommandArguments` of a command.
+In previous versions, the ability has been introduced to access arguments by their node names. However, while this was possible for every other argument, it wasn't possible for `MultiLiteralArgument`s. This was now changed because the values from the `MultiLiteralArgument` are included in the [`CommandArguments`](./commandarguments.md) of a command.
 
 Therefore, the current constructor has been deprecated and the new one should be used:
 
@@ -50,7 +50,7 @@ withArguments(new MultiLiteralArgument("gamemodes", List.of("survival", "creativ
 
 </div>
 
-Because it is possible to list `LiteralArgument`s in the `CommandArguments` of a command, there was also an additional constructor add to the `LiteralArgument` class. The other one is not deprecated.
+Because it is possible to list `LiteralArgument`s in the [`CommandArguments`](./commandarguments.md) of a command, there was also an additional constructor add to the `LiteralArgument` class. The other one is not deprecated.
 
 Now, the `LiteralArgument` class contains two possible constructors:
-Original file line number
+Diff line change
@@ Expand Up / @@ -104,7 +104,7 @@ This won't work, because we make use of a redirect: @@
     \\(\texttt{/execute run} \xrightarrow{redirect} \texttt{mycommand arg1 arg2 arg3}\\)
-    It is not possible to access the `CommandArguments` of previously declared arguments. **If a command occurs via a redirect, the `CommandArguments` of previously declared arguments will be null**.
+    It is not possible to access the [`CommandArguments`](./commandarguments.md) of previously declared arguments. **If a command occurs via a redirect, the [`CommandArguments`](./commandarguments.md) of previously declared arguments will be null**.
     </div>
@@ Expand Down @@