leofuso / argo Goto Github PK

I believe this project can benefit from Gradle Cache functionality, but I need to dig further into it.

I've found a Gradle Plugin built on top of David's plugin that enables dependencies as sources for code generation. It seems like a useful feature so I'm going to try to implement it.

I also need to modify the IDL task to accept multiple classpath configs (why not?).

... preferably using the already implemented workflows

• Register to Portal
• Settle on Plugin ID
• Get Publication Keys
• ... figure out best workflow for publications

CONTEXT

Instead of using markdown to document the plugin usage, one can use the GitHub pages to do so.

PROBLEM / SOLUTION

It can be done using MkDocs.

Update the README.md with actual relevant information regarding the project.

• Ref. to original Avro Plugin
• Guide to Groovy DSL
• Guide to Kotlin DSL
• Ref. to use-cases
• Ref. to supporting different Avro Compiler versions (need to be tested, btw)
• Update all Templates

Since we're dealing with a Gradle task that may or not need to be run accordingly to its Source files track history, we can optimize the primary task to only run on Source files update.

... I'm basically trying to implement all features David managed to implement on his plugin.

I found the parser implementation to be the most challenging part of the project. There's already a version that seems to be working fine, but I need to cover all scenarios to be safe (obviously).

It's time to learn how to unit-test in Gradle!

... also I'll be borrowing all use cases from: https://github.com/davidmc24/gradle-avro-plugin

Scenarios:

• A simple Schema. No dependencies;
• A Schema containing dependencies from somewhere up the chain;
• A Schema containing dependencies from immediately up the chain;
• A Schema containing dependencies from immediately down the chain;
• A Schema containing dependencies from somewhere down the chain;
• A Schema containing unresolved dependencies;
• A Schema containing several dependencies, in reverse order (to stress the iterator);
• A simple Protocol. No dependencies;
• ... can a Protocol have dependencies? Discovery time!