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

1.0 #230

Open
28 of 36 tasks
lastmjs opened this issue Dec 14, 2019 · 0 comments
Open
28 of 36 tasks

1.0 #230

lastmjs opened this issue Dec 14, 2019 · 0 comments

Comments

@lastmjs
Copy link
Owner

lastmjs commented Dec 14, 2019

  • Do not force the user to restart zwitterion to load options and headers files
  • TypeScript
    • Allow passing options to TypeScript compiler
    • Errors to browser console?
  • AssemblyScript
  • Rust
    • Create script to locally download rustc binary for the consumer's machine
      • This is going relatively well, seems to be workingish, some errors to overcome
      • Create a node package that exports rustc functionality as a node module
        • At first we can just compile from the command line with exec or something...it might be nice to find a crate that exposes rustc as a programmatic api. Then we could execute rust code more directly. The ultimate will be when rustc is compiled to wasm
    • Hookup .rs compilation
    • Send compilation and potentially other output to the user's browser console
    • Integrate wasm-bindgen
    • Allow passing options to rustc
    • Figure out the sanitization of the file url...it is not sanitized and goes straight into the shell...is that okay? Zwitterion should only be run locally anyway
    • Improve documentation for Rust
  • Add errors and other output to the browser console
  • Revitalize automated tests, getting them working without Electron if possible, also get them to be deterministic and create a CI pipeline with GitHub Actions
  • Spend a lot of time making the README perfect
    • Add documentation and examples for the headers file
    • Get a couple of people to look over it in its entirety, and observe their qualms
  • Expose the plugin system
    • Document the plugin system
    • Figure out how to allow the plugins to allow the user to specify any filepath for the compiler configuration
  • 100 stars
  • Robust automated tests
    • Arbitrary file contents
    • Arbitrary file and directory structure
  • Get rid of the AssemblyScript inline loader
  • Create a programmatic API...this should simplify testing and stuff
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