Two improvements to the development workflow (#270)

* Configure rust-analyzer to target wasm32-unknown-unknown

* Watch changes to core rust files
This commit is contained in:
bjorn3 2021-07-16 10:49:52 +02:00 committed by Keavon Chambers
parent 546bb16480
commit 9ed1fccd1d
3 changed files with 4 additions and 2 deletions

View File

@ -12,6 +12,7 @@
"editor.defaultFormatter": "dbaeumer.vscode-eslint",
},
"rust-analyzer.experimental.procAttrMacros": true,
"rust-analyzer.cargo.target": "wasm32-unknown-unknown",
"files.eol": "\n",
"html.format.wrapLineLength": 200,
"eslint.format.enable": true,

View File

@ -64,7 +64,7 @@ This is the primary means of running and developing the project. You may need to
npm run serve
```
The server automatically watches for changes to Vue files and rebuilds them. However core Rust and TypeScript file changes require a manual restart of the development server. (Please submit a PR to help it watch the `.ts` files!)
The server automatically watches for changes to Vue files and rebuilds them. However TypeScript file changes require a manual restart of the development server. (Please submit a PR to help it watch the `.ts` files!)
You can also use `npm run lint` and `npm run lint-no-fix` to solve web formatting and `cargo fmt` for Rust formatting. Also `npm run build` writes static files to `/client/web/dist` instead of serving them from memory.

View File

@ -13,6 +13,7 @@ module.exports = {
(Plugin) =>
new Plugin({
crateDirectory: path.resolve(__dirname, "wasm"),
watchDirectories: [path.resolve(__dirname, "../../core")],
})
)
.end();