Two improvements to the development workflow (#270)

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

* Watch changes to core rust files

.vscode/settings.json

@@ -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,
@@ -23,4 +24,4 @@
 		"typescript",
 	],
 	"vetur.format.enable": false,
-}
+}

README.md

@@ -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.
 

client/web/vue.config.js

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