René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Structs: Infer parameter members from functional method signature instead from solely annotations","articleBody":"Currently, ```ParameterStructs``` utility class only check for ```@Parameter``` annotations in order to _structify_ an object. Instead, members should be inferred from the signature of the functional method of the class of the passed object. This should have the following behavior:\r\n* If no ```@Parameter``` annotations are given, the type and the ```ItemIO``` should be inferred from the functional method signature. In doing so, the return type will always be  ```ItemIO.Output``` and method parameters should be ```ItemIO.Input```. If a method parameter is ```ItemIO.Both```, it should be annotated with a ```@Mutable``` annotation. Methods to get the functional method types from a type and the ```@Mutable``` already exists.\r\n* Additionally, the ```@Parameter``` annotations may be given in order to specify the names and further metadata of the member (e.g. required status). Also, this enabled to do fail fast checks if the ```ItemIO``` or the number of parameters does not match the types inferred from the functional method.\r\n* A ```ItemIO.Auto``` was already added in order to indicate that the ```ItemIO``` should be automatically inferred from the functional method. ```ItemIO.Auto``` should be made the default.","author":{"url":"https://github.com/Treiblesschorle","@type":"Person","name":"Treiblesschorle"},"datePublished":"2018-10-12T19:39:09.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/2/scijava/issues/2"}