API requirements should be generated

[sebinside]

Besides writing an Input or Output inside the API project for a new platform source, these in/outputs have also to be registered inside the API. There should be a solution, generating this files, since their content holds no new information.

Another idea would be overloading methods.

See, e.g.: https://github.com/codeoverflow-org/chatoverflow-api/blob/master/src/main/java/org/codeoverflow/chatoverflow/api/plugin/configuration/Input.java

[sebinside]

Current plan: Adding a new annotation to annotate input/output/parameter interfaces in the API. Then, after building the API, a custom sbt task with own class loader loads the API.jar, scanns for annotated interfaces and freshly generates the Input/Output/Parameter Requirement classes, e.g. https://github.com/codeoverflow-org/chatoverflow-api/blob/master/src/main/java/org/codeoverflow/chatoverflow/api/plugin/configuration/Input.java

Then, the API is built again with the new files (which are also commited, still beeing artefacts).

Comments? @joblo2213 @daniel0611

[hlxid]

I think it's fine, no objections.

[J0B10]

👍

[sebinside]

Okay, I need help here: Everything is annotated and I integrated a annotation inspection in the compile process. The idea is to read the generated files, get all annotated interfaces through reflection, generated the files and build again. But I'm not able to import the dependencies correctly. Solutions? @daniel0611

https://github.com/codeoverflow-org/chatoverflow/blob/feature/53-requirements-generator/project/APIUtility.scala#L17

[hlxid]

Sure, I'll look into it tomorrow.

[hlxid]

Apparently /project is a full sbt sub-project, meaning you can just create a file at /project/build.sbt containing the following:

libraryDependencies += "org.reflections" % "reflections" % "0.9.11"

And after a reload in IntelliJ you can import the added dependency successfully.

[sebinside]

Done! This was a great one.