kapi context search

$ kapi search <query>

Ask one question and get the answer from every store the project binds: what this is called and whether it is discouraged, and wording the project has already approved.

Results are grouped by kind rather than merged into one ranked list, because a terminology match and a wording match are not scored on comparable things.

Each term also reports how often the project's extracted content uses it. The count is read from the context graph that extraction writes, so it is as of the last extraction (the last "kapi up") rather than of the working tree: a term added to the store since then shows no uses until the next run.

Commandcontext search

Try it

Runs in your browser against a small sample file. Edit the command before running, or press Run to execute it as shown.

$ kapi context search widget

Flags

Flag	Type	Default	Description
--file	string		explicit path to resource file
--limit	int	10	max results per group
--local	bool	false	use resource in current directory
--locale, -l	string		narrow results to one language
--name	string		named resource in KAPI_HOME (e.g. --name project-terms)
--project, -p	string		path to a kapi.yaml project recipe or its directory (auto-discovered from cwd if omitted)

More examples

$ kapi context search "sign in" --locale en

$ kapi context search widget --json

← Back to the Command Reference