Did You Mean

When the engine corrects a misspelled query, three different things could actually have happened to the search: the corrected term fully replaced the original, both spellings were searched together, or nothing was searched yet and the engine only proposes a correction. <did-you-mean> reads which one from the result and renders the matching message, with links to switch spellings.

Minimal example

import { Component, signal } from "@angular/core";
import { DidYouMeanComponent } from "@sinequa/atomic-angular";
import type { Result } from "@sinequa/atomic";

@Component({
  selector: "results-component",
  imports: [DidYouMeanComponent],
  template: `
    @if (result(); as r) {
      <did-you-mean [result]="r" />
    }
  `,
})
export class ResultsComponent {
  protected readonly result = signal<Result | undefined>(undefined);
}

How it works

Which message renders depends entirely on the resolved action — a computed the component derives from the result, never set directly:

A mixed result — some terms corrected, others expanded — deliberately falls back to suggestion: it is the only one of the three messages that does not assert a specific search behavior that may not actually have happened for every term.

The three messages

Options

selectCorrected() and selectOriginal() are the two methods every message's links call — both patch QueryParamsStore with spellingCorrectionMode: "dymonly" and navigate with the chosen text, so the engine does not re-correct the choice the user just made.

Pitfalls

What's next