[recipes] Add OB1 file converter#349
Draft
alanshurafa wants to merge 1 commit into
Draft
Conversation
alanshurafa
force-pushed
the
codex/file-converter
branch
from
47a0fc7 to
c6c28b9
Compare
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
1 participant
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.
Summary
Adds an offline file converter recipe for turning text, Markdown, JSON arrays, and directories into import-kit-compatible extracted records.
Why
This gives new OB1 users a practical first step for ingesting local files before validation, review, and database import.
Validation
origin/mainmarkdownlint-cli2 --config .github/.markdownlint.jsonc "**/*.md" "#node_modules"-> 0 errorsnpm test --prefix recipes/ob1-file-converter-> 10/10 tests passedgit diff --checkNotes
This is opened as a draft first so the real upstream OB1 checks can run before marking it ready.