Add the Ability to Transform Condition Values After the "when()" Check

[pky920216344]

example:


like this, parameter is null, but "%"+parameter+"%" is not null
When do fuzzy query operation, i must coding:
if(null!=parameter){
xxx.and(column, ()-> "%"+parameter+"%");
}
it's not beautiful

[jeffgbutler]

@pky920216344 Wow - this is a great idea - thanks!

I would implement it more like this:

public IsLike<T> then(UnaryOperator<T> transformer) {
    return shouldRender() ? new IsLike<>(() -> transformer.apply(value())) : this;
}

Then we could write code like this:

SelectStatementProvider selectStatement = select(id, firstName, lastName)
        .from(person)
        .where(firstName, isLike(fName).when(Objects::nonNull).then(s -> "%" + s + "%"))
        .and(lastName, isLike(lName).when(Objects::nonNull).then(s -> "%" + s + "%"))
        .build()
        .render(RenderingStrategy.MYBATIS3);

What do you think?

[jeffgbutler]

If you write a little utility class like this:

public class SearchUtils {
    public static String addWildcards(String s) {
        return "%" + s + "%";
    }
}

Then you can write code like this:

SelectStatementProvider selectStatement = select(id, firstName, lastName)
    .from(person)
    .where(firstName, isLike(fName).when(Objects::nonNull).then(SearchUtils::addWildcards))
    .and(lastName, isLike(lName).when(Objects::nonNull).then(SearchUtils::addWildcards))
    .build()
    .render(RenderingStrategy.MYBATIS3);

I think this qualifies as beautiful 😄

[pky920216344]

@jeffgbutler better than me hope I can use it as soon as possible 😀

[jeffgbutler]

I’ll add this and do a release very soon.

[jeffgbutler]

@pky920216344 this is released and available now in version 1.1.2

[pky920216344]

@jeffgbutler Thank you 😄