Add @Async annotation for the commands/arguments

[vortexthedev]

No description provided.

[SumanohariR]

Hello, I hope you're all doing well!
Could you please confirm whether this issue has already been assigned to someone? If it hasn't it would be a pleasure to contribute to your project!

[chickeneer]

I would confirm that no one is working on this "issue". Truthfully, I have not put any thought into what this looks like to implement. Or anything else about it.

[SumanohariR]

It would be helpful if you could provide a description of the issue! @vortexthedev @chickeneer

[vortexthedev]

It would be helpful if you could provide a description of the issue! @vortexthedev @chickeneer

The title of issue is saying everything

[vortexthedev]

Add @async annotation, so we can get rid of non-async database queries for example in the registered contexts (params).

[vortexthedev]

I would confirm that no one is working on this "issue". Truthfully, I have not put any thought into what this looks like to implement. Or anything else about it.

Could you implement next methods? (If any of registered contexts are async, then the whole command execution will be off main thread by using runTaskAsync?)

CommandManager#registerAsyncContext
CommandManager#registerAsyncOptionalContext
CommandManager#registerAsyncIssuerAwareContext

Add @async annotation so we can select any commands besides the params to be async.

[Joo200]

No, there are some open things:

• How should acf handle async resolvers. Should they be registered and instead of returning the object directly a CompletionStage? Or should the context resolver simply be called async?
• Should the execution of the command be async (off main thread) or rescheduled into the main thread?
• Since it's possible to access values from other arguments with the provided context in the context resolver there should be more information on how to implement this feature for async contexts.

Feel free to make a PoC by forking acf yourself and try to implement such a feature. If anyone could implement that in a few minutes we would already added it as a feature to acf. But such a complex idea should be implemented correctly and the required time for this is huge.

[vortexthedev]

If there is any parameters that are required to be run async, or the command/subcommand has @async annotation, then the whole command process (Command#execute) will be ran through Scheduler#runTaskAsync().
By the command process I mean retrieving the parameters values through registered contexts and running the command method.