> Would the individual commands register via classpath scanning or static
> initializers or is this something that @Endpoint already does for us?
A bit of both as I understand it. Classes containing these endpoint
methods must be explicitly registered in CoreContainer, but from there
reflection i
Would the individual commands register via classpath scanning or static
initializers or is this something that @Endpoint already does for us? In
general, I would be in favor of splitting out the commands, although some
of them might still make sense to group together.
On Thu, Apr 29, 2021 at 4:05
For a long time, I have not been fond of how the code for our collection
APIs are organized. I would prefer to see more separation between the
commands (thus no long class files implementing many commands), and fewer
places to touch generally. If more of a command's logic is in its own
source fil
