-
Notifications
You must be signed in to change notification settings - Fork 86
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
chore: update deploy playground with new backend API #3358
Conversation
|
||
public shared ({ caller }) func getCanisterId(nonce : PoW.Nonce) : async Types.CanisterInfo { | ||
public shared ({ caller }) func getCanisterId(nonce : PoW.Nonce, origin : Logs.Origin) : async Types.CanisterInfo { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duplicating the whole playground backend here in the e2e/assets sure is a lot of technical debt. Can you think of a better way to maintain this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. We can git clone motoko-playground repo and build, instead of hardcoding the code here. We only need to build the pool canister, and it's okay to keep the pre-built wasm-utils.wasm
here. Would be good to do as a follow up PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow-up PR sounds great. Thanks!
Description
dfx deploy --playground
when in CI environment.dfx
. It's only used for monitoring purposes.Checklist: