feat(mcp): export contentDirPath from core/ops#88
Merged
Conversation
The helper already existed in core/ops/paths.ts and backs contentFilePath / documentFilePath, but the subpath barrel only re-exported the file-level helpers. Re-exporting the directory-level resolver lets consumers (Studio) resolve a model's content directory through the same content_path-aware logic instead of keeping a local copy. No behavior change; oxlint and tsc clean. README subpath list now names the four path helpers, changeset is minor (new public API).
✅ Deploy Preview for contentrain-ai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
contentDirPathalready existed incore/ops/paths.ts— it backscontentFilePathanddocumentFilePath— but the@contentrain/mcp/core/opsbarrel only re-exported the file-level helpers. This re-exports the directory-level resolver so consumers resolve a model's content directory through the samecontent_path-aware logic instead of keeping a local copy. Concretely: Studio can drop its last local content-dir helper.Changes
core/ops/index.ts: addcontentDirPathto thepaths.jsre-export (one line, no behavior change)README.md: thecore/opssubpath bullet now names the four path helpersQuality gates
oxlint 0/0,
tsc --noEmitclean. No test changes — nothing imports the barrel in tests and runtime behavior is untouched; the function itself is covered via the plan-API paths that already use it.🤖 Generated with Claude Code