JDL support for filtering is missing in 4.7.0

[shekvl]

Overview of the issue

In 4.7.0, jdl-import generator does not create "jpaMetamodelFiltering": true entries in .jhipster/*.json files (enabling criteria query generation), and there seems to be no way currently to enable such generation from JDL.

Motivation for or Use Case

Without this functionality, it is not possible to correctly update filtering-enabled entities from JDL, as, after every update, the filtering support is switched off (as it defaults to "no").

Reproduce the error

Run jhipster import-jdl with any JDL file and check the resulting .json files.

Related issues

Suggest a Fix

The option like

filtering for <entity-name | *>

can be added to the JDL syntax. Such option, if enabled, should lead to the generation of the "jpaMetamodelFiltering": true entry in .json file for the corresponding entity.

JHipster Version(s)

4.7.0

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

[deepu105]

ping @MathieuAA

[deepu105]

@shekvl the feature is not supported by JDL yet

[MathieuAA]

@deepu105 Roger that, I'll handle it

[jdubois]

Thanks @MathieuAA -> I'm closing this here as this should be handled in jhipster-core

[colameo]

is the keyword 'for' in the 'filter' optional or mandatory?

see example and documentation

They can be used like this: <OPTION> <ENTITIES | * | all> except? <ENTITIES>

in other words, which statement is correct 1 or 2:

entity A
entity B

1. filter * except B
2. filter for * except B

[ruddell]

@colameo The word for is not allowed with filter. Only statement 1 is correct. Please use gitter or stack overflow for questions in the future, this is an issue tracker.

[colameo]

ok, thanks @ruddell

[colameo]

...hm, the documentation is a bit unclear as the 'for' word is allowed for the following options:

skipClient
skipServer
noFluentMethod

...but not for filter.

[ruddell]

@colameo I see your point, it doesn't really make sense why some keywords use for while others do not. I answered based on what worked when importing JDL, JDL Studio should also highlight invalid JDL. This looks like an issue to take up in the jhipster-core project

[MathieuAA]

I'll fix it today.