a4b5tq/repositorybuilder

Automatically build dao interfaces from Entity classes in Maven Project with Spring Data

repositorybuilder's Issues

Preparing for building a repositories methods

Create Constant class with all spring data keywords for sql queries.

Migrate to separate CLI extension and build possible relation filtrations

Imagine the following entities

class Author {
   private int id;
   private String name;
   private List<Book> books;
}

class Book {
   private int id;
   private String name;
   @Unique private String ISBN;
   private List<Author> authors;
   private Cover cover;
}

class Cover {
   private int id;
   private String imagePath;
   private String title;
}

I would like in my AuthorRepository to have all possible permutations of filtration fields and ordering, both for all relational (navigational) properties in the object graph (Filter author by its books, or by its books' cover). Beware from possible graph cycles.

• findByName(name);
• findOneByName(name);
• findByNameOrderByIdAsc(name);
• findByNameOrderByIdDesc(name);
• findByNameOrderByNameAsc(name);
• findByNameOrderByBooksIdAsc(name);
• findByNameOrderByBooksIdDesc(name);
• findByNameOrderByBooksISBNAsc(name);
• findByNameOrderByBooksISBNDesc(name);
• findByNameOrderByBooksNameAsc(name);
• findByNameOrderByBooksNameDesc(name);
• findByNameOrderByBooksCoverIdAsc(name);
• findByNameOrderByBooksCoverIdDesc(name);
• findByNameOrderByBooksCoverImagePathAsc(name);
• findByNameOrderByBooksCoverImagePathDesc(name);
• findByNameOrderByBooksCoverTitleAsc(name);
• findByNameOrderByBooksCoverTitleDesc(name);
• findAllOrderByIdAsc();
• findAllOrderByIdDesc();
• findAllOrderByNameAsc();
• findAllOrderByBooksIdAsc();
• findAllOrderByBooksIdDesc();
• findAllOrderByBooksISBNAsc();
• findAllOrderByBooksISBNDesc();
• findAllOrderByBooksNameAsc();
• findAllOrderByBooksNameDesc();
• findAllOrderByBooksCoverIdAsc();
• findAllOrderByBooksCoverIdDesc();
• findAllOrderByBooksCoverImagePathAsc();
• findAllOrderByBooksCoverImagePathDesc();
• findAllOrderByBooksCoverTitleAsc();
• findAllOrderByBooksCoverTitleDesc();
• ... and so forth for all fields
• findOneByISBN(bookISBN);
• Do not generate findAllByISBN since ISBN is @unique.

As the repository class might grow extremely fast, you can leave the user a chance to create only several methods by some pattern. For example:

• Create only methods with filtration for primitive fields
• Create only methods with ordering only for primitive fields
• Create methods only to certain level of nesting (e.g 1 -> Authors->Books, without Cover)

This could be easily done if you change the configuration as input arguments to your CLI extension. Right now the plugin is bundled to the project and scans entities with annotations, but this highly couples the project to the plugin, but the plugin is used only for one-time startup.

Create a CLI interface that accepts the repository folder where they need to be created and the flags for filtration e.g.

repository-builder.sh /src/main/java/myapp/repository --fields=all
repository-builder.sh /src/main/java/myapp/repository --fields=primitive
repository-builder.sh /src/main/java/myapp/repository --fields=depth(N)

• where N is the nesting level