Skip to content

use buildSpecification surcharge to avoid inconsitencies #32131

@yelhouti

Description

@yelhouti
Overview of the feature request

We have now buildStringSpecification and buildRangeSpecification that do not use function overloads with singleAttribute (only with with RootFunction) making it error prone. I recommend always calling buildSpecification letting the compiler detect the correct function at compile time.
jhipster/jhipster-bom#1804

Motivation for or Use Case

The current behavior is error prone specially when we change filter type or with TextBlob for examples.

  • Checking this box is mandatory (this is just to show you read everything)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions