Uploaded image for project: 'Keikai'
  1. Keikai
  2. KEIKAI-567

configure auto filter with case-sensitive or case-insensitive

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Done
    • Icon: Normal Normal
    • 5.10.0
    • None
    • None
    • Security Level: Jimmy
    • None

      User Story


      As an end-user, I want to filter rows in a case-insensitive way like Excel.


      Acceptance Criteria

      provide a library property to switch between the case-sensitive and case-insensitive ways.

      Comparison

      Case-sensitive

      The current keikai specification.

      How to filter in case-insensitive

      select both upper-case and lower-case items:

      Case-insensitive

      The Excel and Google sheets spec

      Pro

      1. Excel users get used to the case-insensitive way
      2. fewer items in criteria

      How to filter in case-sensitive

      1. add an extra column to flag an item is an upper case or not
      with EXACT()
      2. use advanced filter to filter with EXACT()
      https://www.bluepecantraining.com/portfolio/perform-a-case-sensitive-filter-in-excel/

      Details

      • Currently, keikai shows a drop-down list in a case-sensitive way (the same as ZSS)
      • both ways have their own strength and benefits. Hence, it's better to provide a library property to switch between the case-sensitive and case-insensitive ways.

      Proposed Spec

      Support a application-scoped library io.keikai.filter.caseSensitive, default is true. false means case-insensitive

        1. case-sensitive.jpg
          25 kB
          hawk
        2. googleSheet.jpg
          44 kB
          hawk
        3. keikai-567-case-sensitive-filter.xlsx
          12 kB
          hawk
        4. workaround.jpeg
          23 kB
          hawk

            jumperchen jumperchen
            hawk hawk
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: