Closed levibostian closed 6 years ago
Check out https://github.com/levibostian/Wendy/issues/13 as a potential solution to this. I may not need to do this after all if I simply have Wendy take care of storing the wendy tasks to run.
I took this dependency out with the latest version of Wendy that I will update the code with shortly.
There is no longer the need to register pending API tasks.
Right now, I need Wendy to know about the existence of all pending API tasks in your application. It is a manual process that is annoying.
I would rather have this be more automated. I am thinking to have an annotation that you add to your class that tells Wendy that this is a pending API task. and I can create a Gradle build tool that lints your code and if it finds a class that is ___PendingApiTask (or extends WendyPendingApiTask) then I throw a compile time error for the user to fix it. Or I could have the Gradle plugin generate Kotlin code at compile time to register for me.