experimental tutorial components - #4057
Conversation
✅ Deploy Preview for tauri-v2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
1e0f02f to
444e79d
Compare
store, http-client, sql and logging now source their Manual-setup, usage and permissions code from runner-verified tutorial manifests (plugin-store, plugin-http, plugin-sql, plugin-log) via standalone <TutorialStep>. The Automatic tab and the multi-engine/lang alternatives stay authored prose. Notable content fixes the runner forced: - http-client's floating-await reqwest snippet becomes a real command, exercised against a localhost server in the recorded run - the sql SQLite path proves engine feature selection, migrations and preload end to end; permissions gained the deny-before/allow-after beat - every page's JS usage snippet is now tsc-gated by the recorded build
Review pass over the plugin-page conversion: - TutorialStep expands a recorded `pnpm add <pkg>` mutation into the usual CommandTabs (npm/yarn/pnpm/deno/bun) — the recorded run stays the pnpm one, but readers of the Manual tab keep their manager's command; the four "recorded here with pnpm" disclaimers are gone - trim captions that restated comments already inside the rendered snippets (store usage, sql usage); the $# substitution note is owned by the Syntax section again - re-sync the four manifests: the runner's harness now inherits per field and the add-js-bindings build assertion was dropped as unfalsifiable
8d7ca6d to
299d415
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
… dependency changes
1 participant
so this is more of an idea I had, now I was able to actually try it
basically we render a manifest from this package https://github.com/vasfvitor/tauri-tutorial-runner (I call tatu). If the CI fails, it probably means the tutorial is stale.
in a ai-less world rsbuild.manifest.json would be a pita to maintain, otoh not so sure people will use it, at least llms can use the raw manifest as a baseline to implement features, I could maybe create some evals to see how it goes in a new app and existing app
please don't read the code lmao
tatu runs the manifest on a fresh tauri app
https://deploy-preview-4057--tauri-v2.netlify.app/learn/rsbuild/
will add more manifests/tutorials to see how it behaves and if any headache comes from it