docs: add TI parts engine platform config guide#697
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d57115df0a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## External Vendor Integrations | ||
|
|
||
| You can provide them through a custom platform configuration instead. | ||
|
|
||
| For a concrete example, see | ||
| [Using ti-parts-engine](./using-ti-parts-engine). That guide shows: | ||
|
|
||
| - how to provide a custom TI-backed `partsEngine` | ||
| - how to enable explicit `footprint="ti:..."` strings when needed | ||
| - how to keep partner-token usage in local tooling instead of browser clients | ||
|
|
There was a problem hiding this comment.
I’m not sure we should call out TI specifically in the general platform configuration guide
seveibar
left a comment
seveibar
left a comment
There was a problem hiding this comment.
does this work?
do we support tscircuit.config.ts?
Do not create a ti specific guide, the task was to create a "Using Custom Parts Engines" guide with ti as an example
You have no included the installation step!!!
CC @imrishabh18
|
@techmannih this won't work, why are you writing a doc for something you haven't tested! Please get it working in a tsci dev project!!! |
|
your general steps, other than the installation which is totally incorrect because the package isn't published on npm, are generally correct |
2 participants
Summary
@tscircuit/ti-parts-enginethrough custom platform configurationtscircuit.config.jsonis for serializable JSON settings, not function-valued platform configWhy
These changes make it clearer how to wire TI-backed part lookup and
ti:footprint support into local tooling without implying that this behavior is built into@tscircuit/evalor should live insidetscircuit.config.json.