Ticket #464 (closed enhancement: fixed)

Opened 23 months ago

Last modified 21 months ago

Select filtering mode should match to any part of the string, not just prefix

Reported by: Joonas Lehtinen Owned by: Jani Laakso
Priority: minor Milestone: 4.0.1-rc
Component: Server-side framework Version: 4.0.0-beta2
Keywords: Cc:
Known Issue description:
Hours estimate: 0 Deadline (dd.mm.yyyy):
Known Issue version (since): Known Issue title:
Hours done: Depends to:
Affects documentation: no
Known Issue workaround:
Affects release notes: Contract:

Description

This changes the working logic (to better direction). If there is no oblications, I would do this change

Change History

Changed 22 months ago by Artur Signell

In my opinion the behaviour should be selectable through the API. Sometimes you want the select only to match by prefix, sometimes on substring.

Another way of implementing this would be to add the possibility to specify additional properties that should be prefix-matched. E.g. if I have a list of items "Value / Description" and want the user to be able to search (prefix) on either value or description I could do select.addSearchProperty(DESCRIPTION) and it would check both value (displayed property) and DESCRIPTION property for a prefix match.

Changed 21 months ago by Marc Englund

  • status changed from new to closed
  • resolution set to fixed

OptionStream? filter now changeable

Changed 21 months ago by Jani Laakso

  • hours_left changed from 0.2 to 0
  • milestone changed from Candidates for next release to 4.0.1-rc
Note: See TracTickets for help on using tickets.