'onSelect' return undefined or incorrect element when using search module

[fuhaiq]

Hi,

I am using search module for tag suggestion, here's html code

<div class="ui category tag search">
   <div class="ui icon input">
      <input class="prompt" type="text" placeholder="search tags...">
      <i class="search icon"></i>
   </div>
   <div class="results"></div>
</div>

and this is js code

$.fn.api.settings.api = {
        'tag search': '/tag/search?keywords={query}'
    };
$('.ui.tag.search').search({
        apiSettings: {
            action: 'tag search'
        },
        type: 'category',
        onSelect: function(result, response) {
            console.log(result)
            return false;
        }
    })

This is json returned from server.

{
  "success": true,
  "results": {
    "category1": {
      "name": "Category 1",
      "results": [
        {
          "title": "S1",
          "description": "Optional Description1"
        },
        {
          "title": "S2",
          "description": "Optional Description2"
        },
        {
          "title": "S3",
          "description": "Optional Description3"
        }
      ]
    },
    "category2": {
      "name": "Category 2",
      "results": [
        {
          "title": "S10",
          "description": "Optional Description10"
        }
      ]
    }
  }
}

All the results displayed correctly, I want do some js hack when clicking the element, so I use onSelect callback.
'S10' is logged correctly, but 'S2' and 'S3' returned 'undefined' in console after click

More weird is when I click 'S1', console shows 'S10' element

Please take a look, thanks!

[jlukic]

There were fixed related to this in one of the last patch releases. I'm on my phone but check closed issues.

Are you using latest?

[fuhaiq]

@jlukic Yes. I am using 1.11.6. And this could be reproduced when using the master version from download as well

[jlukic]

Thanks for the clarification. I'll take a look

[jlukic]

Investigating this now, thanks for your patience.

[jlukic]

I've reworked the offending method, it was a pretty poor implementation previously, and some of the variable names were a bit confusing.

I've verified against your example using the new $.api({ mockResponse: 'foo'}); syntax which I've also added as a new feature.

[jlukic]

Available with 2.0

[fuhaiq]

Cheers!