feat: Add functionality to incorporate directly markdown content (as string) when inserting documents #96
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.
This PR introduces the ability to directly pass markdown content as input when inserting documents into the database. Previously, only file paths (e.g., PDF) were supported, but with this change, users can now input a markdown string directly, making the process more flexible.
Changes:
This change improves the workflow for users who need to insert markdown content directly, without requiring it to be written to a file first.
Testing:
This PR has been tested locally with a local setup.
Markdown data is correctly stored in the local sqlite database with the insert document functionality.