Clarify usage section in README.md

[postmeback]

There were certain installation steps missing in the ReadMe file, which I added in order to get it corrected.

[jedel1043]

IIRC cargo run -- test is equivalent to cargo build & cargo run -- test, so I don't see why this should fail. Do you have an error log that we could look at?

[postmeback]

I restarted my system, and executed "cargo run -- Hello2.js", it ran successfully. But after installation, when I was trying to do so, it was failing. Sorry, I don't have any screenshots of that.

Today's success.

[postmeback]

It gives the person a clear idea to where the file should be added; it's worth mentioning.

[HalidOdat]

It gives the person a clear idea to where the file should be added; it's worth mentioning.

It doesn't have to be in the root dir, it just require a path to the file. so cargo run -- ../some-folder-outside-root/works.js

[postmeback]

@HalidOdat , you are correct. But if somebody changes the directory to the target folder, and then runs cargo-run, then it will fail. I think, for better clarity, we should be mentioning it.

[postmeback]

Although, alternative suggestions are always welcome

[HalidOdat]

@HalidOdat , you are correct. But if somebody changes the directory to the target folder, and then runs cargo-run, then it will fail. I think, for better clarity, we should be mentioning it.

This, should be obvious, cargo doesn't work if Cargo.toml is not found (applies to pretty much every build system)

Although, alternative suggestions are always welcome

We can make it explicit:

"Run with cargo run -- test.js in the project root directory where test.js is a path to an existing JS file with any JS valid code."

[postmeback]

@HalidOdat I would request you to put suggestions in this PR. That would be helpful.

[nekevss]

It may be a bit more succinct to write.

 - Run with `cargo run -- test.js` in the root directory where `test.js` is a path to any existing valid JS file.

Do we need to double reference JS file and valid JS code?

[postmeback]

Double reference is not needed.

[postmeback]

It may be a bit more succinct to write.

 - Run with `cargo run -- test.js` in the root directory where `test.js` is a path to any existing valid JS file.

Do we need to double reference JS file and valid JS code?

It looks perfect.

[postmeback]

Hi, I have updated the steps as per the discussion. requesting for review and merge.

[postmeback]

For the first time, to be on the safer side, I believe we should mention this step.

[HalidOdat]

I don't think this is needed, cargo should always build if you run (and it is not already built). If it doesn't, that means it is a bug in cargo and should be reported in the cargo repo https://github.com/rust-lang/cargo/

[Razican]

Note that we should still remove the cargo build part, since it's not needed and is adds complexity to the steps.

[postmeback]

Removed that part.

[codecov]

Codecov Report

Merging #3092 (72f8314) into main (ce520fa) will decrease coverage by 0.02%.
Report is 78 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3092      +/-   ##
==========================================
- Coverage   50.42%   50.40%   -0.02%     
==========================================
  Files         444      436       -8     
  Lines       45877    42375    -3502     
==========================================
- Hits        23132    21358    -1774     
+ Misses      22745    21017    -1728     

see 228 files with indirect coverage changes

[postmeback]

Hey, can this be merged ?