Use Rust for the front-end too #374

已合併

elegaanz 於將 11 次代碼提交從 wasm 合併至 master

elegaanz " 評論 " (Migrated from github.com)

Rust can compile to WASM, so let's use it for front-end code as well.

To compile the front-end:

cargo install cargo-web
cd plume-front
cargo web deploy -o ../static

Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cd plume-front cargo web deploy -o ../static ```

trinity-1686a reviewed

trinity-1686a left a comment

所有者

I've had a hard time testing this. I think it would be better to cargo web deploy without location, and do some processing (adding static/ to path so the new route is not required) and copying by ourselves in build.rs. Currently the instructions are polluting static/ with an index.html

I've had a hard time testing this. I think it would be better to `cargo web deploy` without location, and do some processing (adding `static/` to path so the new route is not required) and copying by ourselves in build.rs. Currently the instructions are polluting `static/` with an `index.html`

static/plume-front.js

trinity-1686a " 評論 "

所有者

I think this file souldn't be committed, it's auto generated and things like __cargo_web_snippet_199d5eb25dfe761687bcd487578eb7e636bd9650 are probably not reproducible between builds

I think this file souldn't be committed, it's auto generated and things like `__cargo_web_snippet_199d5eb25dfe761687bcd487578eb7e636bd9650` are probably not reproducible between builds

elegaanz " 評論 " (Migrated from github.com)

You can now just use cargo web deploy, build.rs will do the rest.

You can now just use `cargo web deploy`, build.rs will do the rest.

👍 1

igalic " 評論 " (Migrated from github.com)

how much faster is the resulting wasm compared to the previous Javascript?

trinity-1686a " 評論 "

所有者

@igalic considering our use-case, probably not much. The main advantage is the whole team being able to debug it I think

👍 2

elegaanz " 評論 " (Migrated from github.com)

There may be better performances once with the future editor, especially when writing big articles. Another advantage is that we will be able to share code between backend and frontend if we need it.

👍 1

trinity-1686a " 評論 "

所有者

@BaptisteGelez I see Travis failed because of cargo-web installation, you might be interested into this https://github.com/koute/cargo-web#using-cargo-web-on-travis .

👍 1

codecov[bot] " 評論 " (Migrated from github.com)

Codecov Report

Merging #374 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #374   +/-   ##
=======================================
  Coverage   27.86%   27.86%           
=======================================
  Files          63       63           
  Lines        6280     6280           
=======================================
  Hits         1750     1750           
  Misses       4530     4530

# [Codecov](https://codecov.io/gh/Plume-org/Plume/pull/374?src=pr&el=h1) Report > Merging [#374](https://codecov.io/gh/Plume-org/Plume/pull/374?src=pr&el=desc) into [master](https://codecov.io/gh/Plume-org/Plume/commit/22bc8c1d407cd4c3844aaa1161afd2a86f6d349a?src=pr&el=desc) will **not change** coverage. > The diff coverage is `n/a`. ```diff @@ Coverage Diff @@ ## master #374 +/- ## ======================================= Coverage 27.86% 27.86% ======================================= Files 63 63 Lines 6280 6280 ======================================= Hits 1750 1750 Misses 4530 4530 ```

trinity-1686a reviewed

trinity-1686a left a comment

所有者

You should also update documentation, something like add "run cargo web deploy -p plume-front"

You should also update documentation, something like add "run `cargo web deploy -p plume-front`"

.gitignore

trinity-1686a " 評論 "

所有者

this line is no longer required

trinity-1686a approved these changes

Reviewers

trinity-1686a approved these changes

The pull request has been merged as 3fce5d6a14.

You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.

git checkout -b wasm master

git pull origin wasm

Step 2:

Merge the changes and update on Forgejo.

git checkout master

git merge --no-ff wasm

git push origin master

登入才能加入這對話。

No reviewers

未選擇里程碑

No Assignees

2 參與者

訊息

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Loading…

尚未有任何內容

標籤 里程碑

Use Rust for the front-end too #374

Codecov Report

Reviewers

Step 1:

Step 2:

標籤里程碑