-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add playground page to astro docs #111
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Is it easy for you to add versioning to this playground? Basically, changing the version should change the WASM file. If we can add it, I can build Ada wasm and add those multiple files in a follow up PR |
we can land it with tailwindcss and remove it in a follow up pull request |
I don't understand the request, it is using the same wasm file as the current site. Do we need to add a choice for which wasm file to pick up? Also would it be a code based config or a url based one? |
Also right now tailwind is not setup to work with the astro site. I'm not sure if it'd be conflicting with the current tailwind config as it is in the same root. Other components added earlier are also using vanilla css instead of tailwind. |
Let's land it with vanilla css then. I was thinking about adding a dropdown to playground with different versions (such as 2.9.0, 2.9.1 etc) which changes the version of Ada. Currently we have 1 version (only 1 wasm file) but if we add the versioning support it would be super easy to add more. |
client:load renders HTML on the server/build and loads and hydrates js on the client, as opposed to client:only which loads, renders and hydrates only on the client
Hello, I've added a drop-down for different versions. If you could add the wasm files and the corresponding wasm.js I can test the changes out. |
Tasklist
utils.ts
without site config from next