searchFullText setting has been renamed fullTextSearch for c

Error message

searchFullText setting has been renamed fullTextSearch for consistency, please adjust your settings.

What it means

A rename/deprecation notice. In get.settings() (search.js:406-410), if the parameters passed to .search(...) contain the legacy searchFullText flag, search copies it onto settings.fullTextSearch and logs error.oldSearchSyntax. The feature still works; this is a console warning telling you to migrate the option name.

Source

Thrown at src/definitions/modules/search.js:1304

  className: {
    animating : 'animating',
    active    : 'active',
    empty     : 'empty',
    focus     : 'focus',
    hidden    : 'hidden',
    loading   : 'loading',
    results   : 'results',
    pressed   : 'down'
  },

  error : {
    source          : 'Cannot search. No source used, and Semantic API module was not included',
    noResults       : 'Your search returned no results',
    logging         : 'Error in debug logging, exiting.',
    noEndpoint      : 'No search endpoint was specified',
    noTemplate      : 'A valid template name was not specified.',
    oldSearchSyntax : 'searchFullText setting has been renamed fullTextSearch for consistency, please adjust your settings.',
    serverError     : 'There was an issue querying the server.',
    maxResults      : 'Results must be an array to use maxResults setting',
    method          : 'The method you called is not defined.'
  },

  metadata: {
    cache   : 'cache',
    results : 'results',
    result  : 'result'
  },

  regExp: {
    escape     : /[\-\[\]\/\{\}\(\)\*\+\?\.\\\^\$\|]/g,
    beginsWith : '(?:\s|^)'
  },

  // maps api response attributes to internal representation
  fields: {

View on GitHub (pinned to 597843ab84)

Solutions

Rename the option: replace searchFullText with fullTextSearch.
Use the string 'exact' for exact matching or true for fuzzy full-text matching under the new name.
Remove the option entirely if the default behavior is acceptable.

Example fix

// before
$('.ui.search').search({ source: data, searchFullText: true }); // logs [86]

// after
$('.ui.search').search({ source: data, fullTextSearch: true });

Defensive patterns

Strategy: validation

Validate before calling

// Migrate legacy option name before init
if ('searchFullText' in cfg) { cfg.fullTextSearch = cfg.searchFullText; delete cfg.searchFullText; }
$('.ui.search').search(cfg);

Prevention

Use fullTextSearch (true | 'exact') instead of searchFullText.
Update config copied from older docs/examples.
Grep the codebase for searchFullText after upgrades.

When it happens

Trigger: Calling $('.ui.search').search({ searchFullText: true, source: data }) — the presence of parameters.searchFullText triggers the warning at search.js:407-409.

Common situations: Copying config from an older Semantic UI example or pre-2.x docs; upgrading the library without updating option names; tutorials that predate the rename.

Related errors

AI-assisted analysis of Semantic-Org/Semantic-UI@597843ab84 (2026-08-13). Data as JSON: /api/errors/1f44462f20f2698b. Report an issue: GitHub.