@@ -102,7 +102,7 @@ repositories {
102102 mavenCentral()
103103}
104104dependencies {
105- implementation(" net.kautler:command-framework:0.6 .0-SNAPSHOT" )
105+ implementation(" net.kautler:command-framework:0.7 .0-SNAPSHOT" )
106106}
107107```
108108
@@ -116,7 +116,7 @@ you can request the according feature variants like this:
116116
117117``` kotlin
118118dependencies {
119- implementation(" net.kautler:command-framework:0.6 .0-SNAPSHOT" ) {
119+ implementation(" net.kautler:command-framework:0.7 .0-SNAPSHOT" ) {
120120 capabilities {
121121 requireFeature(" javacord-support" )
122122 }
@@ -140,7 +140,7 @@ _**Published Feature Variants:**_
140140<dependency >
141141 <groupId >net.kautler</groupId >
142142 <artifactId >command-framework</artifactId >
143- <version >0.6 .0-SNAPSHOT</version >
143+ <version >0.7 .0-SNAPSHOT</version >
144144</dependency >
145145```
146146
@@ -304,7 +304,9 @@ If your command needs parameters or you want to do other customizations of the `
304304` SlashCommandJda#prepareSlashCommandData ` method, which just returns the argument in its default implementation.
305305In the implementation of the method you can then use the full API for JDA slash commands. For subcommands you instead
306306overwrite the ` SlashCommandJda#prepareSubcommandData ` method, which has the same default implementation and customizes
307- a ` SubcommandData ` .
307+ a ` SubcommandData ` . When having subcommands, Discord does not allow to have the top-level command as actual command
308+ itself. In this framework you can though still have that top-level command to customize the ` SlashCommandData ` for that
309+ parent of the subcommands, for example to set the integration types or contexts.
308310
309311When using [ command context transformers] ( #customizing-the-command-recognition-and-resolution-process ) with slash
310312commands, all phases before ` BEFORE_COMMAND_COMPUTATION ` are skipped by the command handler already.
0 commit comments