The (unofficial) API for Obsidian.md searching functionality.
Obsidian does not provide an API for using it's search functionality, forcing developers to either build their own - with limited features, depend on something like dataview, or perform a gross hack in which we query the DOM of the search plugin. NO MORE
This library provides a parse
function to convert a query string into a FileFilter, a search
function to directly query the app from a given query, and direct access to the corresponding FileFilters.
This library is still in ALPHA due to limited test coverage. Use at your own risk!
# Using npm
npm install obsidian-search
# Using yarn
yarn add obsidian-search
import { search } from 'obsidian-search'
const asyncResults = search(`file:filename OR path:sub/folder OR [has property:with value]`, app) // the App made available to your plugin
for await (const file of asyncResults) {
// do something with the file
}
Of course, the query provided could be a string
that your users passed into an input somewhere.
If you need more direct access to the file filters for finer control over when and how you filter for files, you may also use the parse
function:
import { parse } from 'obsidian-search'
const filter = parse(`file:filename OR path:sub/folder OR [has property:with value]`, app.metadataCache) // the App made available to your plugin
const files = app.value.getMarkdownFiles();
for (const file of files) {
if (await filter.appliesTo(file)) {
// do something with the file
}
}
Thank you for considering contributing to the obsidian-search
library! Contributions are welcome and encouraged.
If you find a bug or have a feature request, please open an issue on the issue tracker. When creating an issue, provide as much detail as possible, including steps to reproduce for bugs.
If you would like to contribute directly to the codebase, you can follow these steps to submit a pull request:
-
Fork the repository.
-
Create a new branch for your feature or bug fix:
git checkout -b feature-name
-
Write new tests for your changes if applicable.
-
Run the tests to ensure nothing broke (and your changes work):
npm run test:unit
-
Commit your changes:
git commit -m "Add your commit message here"
-
Push your branch to your fork:
git push origin feature-name
-
Open a new Pull Request from the feature branch in your fork