Typesense v1#83
Draft
clarkd wants to merge 1 commit into
Draft
Conversation
🧩 Plugin PR Summary📦 Modified Plugins
📋 Results
🔍 Validation Details✅
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔌 Plugin overview
multi_searchJSON queries, and result-count summaries against a Typesense Cloud (or self-hosted) instance — without ever needing admin access to the cluster.documents:searchaction) sent in theX-TYPESENSE-API-KEYheader.🖼️ Plugin screenshots
Plugin configuration
To add: screenshot of the Host URL / Search API Key / Collection setup form.
Default dashboards
To add: screenshot of the Overview dashboard (Total Documents + Search Time KPIs, Documents table).
🧪 Testing
Every stream was built and tested against a live, authenticated tenant (region
dev) usingsquaredup test, against a real collection (companies-production-en-us, ~10,633 documents):q=*search against the configured collection returns200 OK; confirms host, key, and collection in one probe.documentSearch— returns one row per matching document with dynamic per-collection columns plus a relevance score; verified that unset optional params (query_by/filter_by/sort_by) are correctly dropped, and that relevance populates on real text queries.multiSearch— rawPOST /multi_searchfrom a JSON blob; verified the configured collection is auto-injected as a query-arg default, so a minimal{"searches":[{"q":"*"}]}blob queries the right collection with nothing extra.searchSummary— single count row (found/out_of/search_time_ms); verifiedper_page=0returns counts with zero hits transferred.squaredup validate --jsonpasses: 4 data streams, icon, UI config, config validation, and default content all present.collections:listneeds an admin key). This is a query-on-demand plugin with no imported objects (hence no perspectives).per_page); search is designed to return the most relevant results, not to bulk-export a collection.per_pageand field counts reasonable, or narrow withfilter_by.timeframes: false). To restrict by time, add afilter_byon a timestamp field.📚 Checklist