@maschinenlesbar.org/marktstammdatenregister-cli
    Preparing search index...

    Function filterProblem

    • Describe why the register would misread a filter spec, or return undefined when the spec is fine. The spec is read the way the register reads it — split on every ~ into FilterName, operator and value, conditions joined by and — and must have that shape:

      • every condition has a non-blank FilterName, a known lower-case operator and a value ('' for null/nn: Ort~null without a value is ignored upstream and returns the unfiltered register); for the other operators the value is not blank, quoted ('', ' ') or not;
      • a value that starts with a single quote ends with one;
      • conditions are joined by and only, and nothing dangles at the end.

      ~or~ is refused: the live search keeps only the part before the first ~or~ and drops every later condition without an error (checked 2026-09-26: wind 2497 alone 43633, 2497~or~…2498 also 43633). An OR between codes of one dropdown column works as a comma list inside one value: Energieträger~eq~'2497,2498' (52448 = 43633 + 8815).

      An unknown FilterName cannot be checked here (the register ignores it and returns the unfiltered set); compare with filterColumns().

      Parameters

      • spec: string

      Returns string | undefined