ink-playground
ink-playground copied to clipboard
use-ink
Browser Based Playground for editing, sharing & compiling ink! Smart Contracts
This is the backend implementation for Issue #125
Currently all lgging is doen by `println!`. We should switch to a proper logging solution: - [ ] replace all `println!` statements in all creats by `log` macros - [...
I think it would be cool to have some sort of service that subscribes via webhooks to new `ink!` and/or `cargo-contract` releases and automatically updates the `compiler` and `contract` TOML...
Currently, test in Jest are slow due to ESM transpilation. Plus, we can not test the `monaco` editor/ rust anayler functionalities properly. Most likely Cypress unit testing would allow for...
We should add support for supplying an ink! version to be used for the playground in the URL. This is necessary to allow links to the playground remain working, independent...
Rustdoc supports a feature for defining a playground URL: ```rust #![doc(html_playground_url = "https://playground.example.com/")] ``` https://doc.rust-lang.org/rustdoc/write-documentation/the-doc-attribute.html#html_playground_url We can use this feature to have a "Run" button show up in our ink!...
Currently, ink! Playground can interpret and compile only one specific version of ink!. To make the playground useful for tutorials and also to share code snippets in forums, we need...
Check the currently used Dockerfile: https://github.com/achimcc/ink-backend/blob/main/compiler/Dockerfile Used by https://github.com/achimcc/ink-backend/blob/main/src/sandbox.rs to compile ink! Smart Contracts to WASM Try to opmtimize the build performance. Currently the build process slows down drastically if...