-
Notifications
You must be signed in to change notification settings - Fork 39
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
ref(wasm-dpp): simplify scripts/build-js.sh for readability and testability #1697
Conversation
Co-authored-by: Ivan Shumkov <[email protected]>
…-check (dashpay#1647) Co-authored-by: Ivan Shumkov <[email protected]>
…ommitted (dashpay#1663) Co-authored-by: Quantum Explorer <[email protected]>
Co-authored-by: QuantumExplorer <[email protected]>
Co-authored-by: QuantumExplorer <[email protected]>
Co-authored-by: Odysseas Gabrielides <[email protected]> Co-authored-by: Ivan Shumkov <[email protected]>
Co-authored-by: Odysseas Gabrielides <[email protected]> Co-authored-by: Ivan Shumkov <[email protected]>
Co-authored-by: Djavid Gabibiyan <[email protected]> Co-authored-by: Dmitrii Golubev <[email protected]> Co-authored-by: strophy <[email protected]> Co-authored-by: QuantumExplorer <[email protected]> Co-authored-by: fominok <[email protected]> Co-authored-by: Ivan Shumkov <[email protected]> Co-authored-by: markin.io <[email protected]>
479f3fe
to
3e4d8c5
Compare
It doesn't seem working |
… attacks (dashpay#1681) Co-authored-by: markin.io <[email protected]> Co-authored-by: Lukasz Klimek <[email protected]> Co-authored-by: Ivan Shumkov <[email protected]>
dashpay#1705) Co-authored-by: Quantum Explorer <[email protected]>
Co-authored-by: QuantumExplorer <[email protected]>
@shumkov I just ran it again now and it's still working for me. pushd ./platform/packages/wasm-dpp/
sh ./scripts/build-js.sh
Can you clarify what you mean by "not working"? Are you getting an error message? Is some artifact not being produced as you expected? |
Possibly because pipelines are failing on this PR, but I'm not quite sure what the reason is. Is it because PR was created from repo fork? |
500700f
to
8e3b7e8
Compare
@shumkov I rebased off of the latest and I did find a problem. The original had an error in its quotes, but it also had an error it its I updated this to use |
@shumkov The PR checks always fail for me. I'm not a member of the
See: |
Makes it easier to copy/paste to test or run locally.
This had a bunch of variables for things that were actually constant strings with no variability, which made it look much more complex, and much more difficult to understand the full context of.
This simplifies it to only use variables where the output is non-constant or used many times.
Issue being fixed or feature implemented
build-wasm.sh
, assumingcargo build was run
)shellcheck
&shfmt
What was done?
This was a bit over-variable-ified for strings that were actually constant and not used more than twice.
How Has This Been Tested?
I just ran it the normal way.
Checklist:
For repository code-owners and collaborators only