Feature request #8893
raise warning if an expression cannot be evaluated.
| Status: | Open | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Unknown | ||
| Pull Request or Patch supplied: | No | Resolution: | |
| Easy fix?: | No | Copied to github as #: | 17571 |
Description
Hi,
when opening an existing project using expressions or sql queries in Rule based classes or labels or feature subset, if expression cannot be evaluated, no warning is raised.
For example, the data field names have changed.
User have some empty classes, or totally empty classes or labels, and finding why can be long.
Having a soft warning would be sufficient. Something like "expression XXX on layer (labeling / style) could not be evaluated... please check"
Cheers
Régis
Related issues
History
#1
Updated by Giovanni Manghi over 7 years ago
- Easy fix? set to No
#2
Updated by Jürgen Fischer about 7 years ago
- Category set to Unknown