-
Notifications
You must be signed in to change notification settings - Fork 25
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
Update w3ui website examples #138
Comments
does it make sense to bring those examples into this repo, and then put them into the test suite? eg the website would just pull the files from this repo during build. and the tiny example would be part of the test suite here. (If we decide to do this, we should track it in a new issue) |
which work are you referring to? looks like @yusefnapora already started on it |
@dchoi27 setup a test suite for the examples to eventually go into. It may not make sense right now but given the pace at which things change, it might be helpful? |
ah i see! |
I think creating the core test suite would be a core engineering thing. Once it is in place, maintaining it can be support |
closes storacha/w3ui#138 The big change (apart from the example content) is that I added `raw-loader` so we can import the code samples from files instead of embedding the source into the page. Apparently in webpack 5 you're supposed to use [asset modules](https://webpack.js.org/guides/asset-modules/) instead, but I wasn't able to make it give me the original source - it wants to transpile everything with SWC first. I fought with it for an hour before giving up and using `raw-loader`, which still works fine despite its deprecated status. updated / reviewed examples: - [x] keyring - [x] react - [x] solid - [x] vue - [x] uploader - [x] react - [x] solid - [x] vue - [x] uploads-list - [x] react (no changes) - [x] solid - [x] vue (no changes)
The code snippets on the website need updating. They are simplified, and mostly just have styles removed, but also have some code simplifications to make it as easy as possible to understand.
refs #117
The text was updated successfully, but these errors were encountered: