Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs fiddle: Pre-defined outputs / caching #33

Open
Akeboshiwind opened this issue Apr 23, 2024 · 1 comment
Open

docs fiddle: Pre-defined outputs / caching #33

Akeboshiwind opened this issue Apr 23, 2024 · 1 comment

Comments

@Akeboshiwind
Copy link
Collaborator

Mentioned in https://codapi.org/faq/, seems good for if the fiddle is down for some reason.
This is also similar to an idea by @/mal to run the examples at docs build time to ensure they at least run, even if they aren't tested.

@Akeboshiwind Akeboshiwind changed the title Pre-defined outputs docs fiddle: Pre-defined outputs May 14, 2024
@Akeboshiwind Akeboshiwind changed the title docs fiddle: Pre-defined outputs docs fiddle: Pre-defined outputs / caching May 14, 2024
@Akeboshiwind
Copy link
Collaborator Author

The way I was thinking of getting this working was:

  • Parse mdx files using rehype or something (not ideal tbh)
  • Get the inputs (ignoring e.g. the Text input)
  • Generate all combinations of values and run the fiddle for all those
  • Store in a global variable somewhere on the page

Not sure if this would get too big for some fiddles 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant