google / callbuilder Goto Github PK

Since all the builder classes that CallBuilder generates are currently dropped into the same namespace, there's a chance that class names will conflict.
To work around that, one can use a longer class name (perhaps prefixed with the name of the method that will be called). This could result, though, in very long class names.

Can you please enhance CallBuilder so that we can specify a sub-package in which the generated builder class will reside?

e.g.

package foo.bar;
class Baz {
    CallBuilder(className="builder.GenerateQuxBuilder")
    public static Qux generateQux();
}

will create foo.bar.builder.GenerateQuxBuilder.
This can then be imported as GenerateQuxBuilder with no risk of conflicts.

Alternatively, you can add an attribute to the annotation to specify the package name separately.

There should probably be two release jars:

• plugin deploy jar, which has a file at META-INF/services/javax.annotation.processing.Processor with the class name of the processor implementation
• annotations-only jar, which lets you use the @CallBuilder and @BuilderField annotations in your app.

The former can be added to the processor_path while the latter can be added to the compile-time and run-time classpath, OR the former can be added to all three if you are not concerned about the size of your release jar.

It doesn't have to be a genrule necessarily - just some automated, reproducible method for creating the jars.

Default values can be potentially supported by automatically calling a function before building:

@CallBuilder
Person person(String name, int age) {...}

void person_preBuild(PersonBuilder builder) {
  if (builder.getAge() == 0) builder.setAge(30);
}

Where {methodName}_preBuild is an optional method that is called by the build() method automatically if supplied.

Generated classes should be annotated with javax.annotation.Generated.
Similar to how AutoValue annotates its generated classes:
@ Generated("com.google.auto.value.processor.AutoValueProcessor")

Having a release in maven central would be nice. :)

Hey, I find this project occasionally, it's really a good idea.
But the wiki link seems broken, I've no idea how to use it.
Can anyone help to give a user guide doc?