-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add saber-plugin-search #366
feat: add saber-plugin-search #366
Conversation
Deploy preview for saber ready! Built with commit a9583b2 |
Here's a demo where you can see it in action: https://deploy-preview-31--saber-theme-tailsaw.netlify.com/ |
Co-Authored-By: Koyuki (EGOIST) <0x142857@gmail.com>
what about adding an option to allow more search strategies? e.g. |
I unfortunately can't fully test it at the moment, but I'll try to do it when I'm back home in a couple of days. If someone of you wants to experiment in the meantime, feel free to do so :) |
Updated preview with Tailsaw: https://5d5e79095fbf530008ae7f60--saber-theme-tailsaw.netlify.com/ |
* feat: saber-plugin-local-search * fix: only add valid pages * use global public url Co-Authored-By: Koyuki (EGOIST) <0x142857@gmail.com> * shorten syntax * rename plugin to `saber-plugin-search` * feat: add multiple adapter support * make it more low-level * strip html tags * Add LICENSE * tweaks
It's in master but the PR is not marked as merged 🤔 |
Yes GitHub |
Alright, lol. I'll wait on the next package publish so the canary flag gets removed, then I'll merge in the Tailsaw search PR. |
Published |
Summary
saber-plugin-local-search
adds a hyper-fast, easy to integrate and highly customizable search to your app. See README for more.What kind of change does this PR introduce? (check at least one)
If changing the UI/CSS related code, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx]
, where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:
Original issue: saberland/saber-theme-tailsaw#5
Published PR with canary version:
Canary Versions
extract-sfc-blocks@0.0.3-canary.366.524f251.0
create-blog@0.2.8-canary.366.524f251.0
create-site@0.3.2-canary.366.524f251.0
saber-highlight-css@0.1.1-canary.366.524f251.0
saber-highlighter-prism@0.3.2-canary.366.524f251.0
saber-log@0.2.1-canary.366.524f251.0
saber-markdown@0.1.1-canary.366.524f251.0
saber-plugin-feed@0.4.1-canary.366.524f251.0
saber-plugin-git-modification-time@0.1.1-canary.366.524f251.0
saber-plugin-google-analytics@0.1.1-canary.366.524f251.0
saber-plugin-image@0.1.1-canary.366.524f251.0
saber-plugin-meta-redirect@0.1.1-canary.366.524f251.0
saber-plugin-netlify-redirect@0.1.1-canary.366.524f251.0
saber-plugin-prismjs@0.2.2-canary.366.524f251.0
saber-plugin-pwa@0.4.1-canary.366.524f251.0
saber-plugin-query-posts@0.4.1-canary.366.524f251.0
saber-plugin-search@0.0.2-canary.366.524f251.0
saber-plugin-transformer-html@0.1.1-canary.366.524f251.0
saber-plugin-transformer-pug@0.1.1-canary.366.524f251.0
saber-utils@0.2.1-canary.366.524f251.0
saber@0.7.1-canary.366.524f251.0