Version 1.6.2

Features

• Legacy support for systems that are unable to match ListingParamters.addFilterAttributes(String, Object) anymore.
• Happy 1st Birthday Simon! 🥳

Version 1.6.1

Features

• ListingParameters.addFilterAttributes() isn't limited to String anymore. So you don't have to stringify numeric or enum values anymore.

Version 1.6.0

Features

• Visual table summary? Want to know what's the most of something? No problem! You can acquire terms and statistics by just throwing attribute names into filter! Have a look at Visual Table Summary in this UX Collective article.
• Fetch size optimization can be applied by ListingConfig.FETCHSIZE, witch will add typedQuery.setHint("org.hibernate.fetchSize", ListingConfig.FETCHSIZE); to the query if set.
• Convenient new ListingParameters constructors with parameters page & limit and only limit

Version 1.5.1

• New filter operator AND ('&')
  • Ever wondered what German city has double A and double L in its name? Attribute: city Filter: aa&ll - it's Halle an der Saale
  • Lets see, what Eike did in December 2018! Attribute: createdBy|createdAt Filter: Eike AND 12.2018

Release 1.5.0

Features

• Date filter values accept any character now, not only dots, e.g. 04-10-1983
• Date filter values accept now also two digit years, e.g. 04-10-83
• Date type now accepts current milliseconds as filter values

BREAKING CHANGES

• @ListingLikeOnNumber got replaced by @ListingFilterAsString and is no more

Bug Fixes

• Made date filter pattern MM.YYYY work

Version 1.4.10

Features

• Collection fields are now accessible if annotated with @ListingLikeOnNumber. This only makes sense, if the database field can be string represented!

Version 1.4.9

Features

• @ListingFilterAsString replaced now deprecated @ListingLikeOnNumber. This new annotation will cast any type to string to match a filter.
• Configurable boolean values ListingConfig.BOOLEAN_TRUE and ListingConfig.BOOLEAN_FALSE to customize the filter.
• New ListingConfig.URI_DECODE flag decides if string values that are provided by the URL (sortAttribute, filter, filterAttributes) gets URI decoded (Default: false).

Version 1.4.8

Features

• To avoid a limitation of the result list you can now set the limit to zero: listingParameters.setLimit(0);

Bug Fixes

• Keywords like AND, LIKE, NOT, etc gets escaped before being used in regular expressions. So there is more possibilities when using custom keywords.
• Using a page number without limit doesn't start at the first element of the total result list anymore
• URI character encoding configurable (default is UTF8)

Minor Bugfix

Preventing stack overflow if there are to many disjunction in an filter value.

Minor Bugfix

Fixed handling with empty attribute filter values.