Skip to content
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

Merged
merged 6 commits into from
Sep 15, 2023
Merged

Conversation

chenyan-dfinity
Copy link
Contributor

@chenyan-dfinity chenyan-dfinity commented Sep 8, 2023

Description

  • Error out dfx deploy --playground when in CI environment.
  • Report to the playground backend that this request comes from dfx. It's only used for monitoring purposes.
  • Sync the API with Add stats by origin motoko-playground#192
  • No changelog update needed, as the playground feature is already in the changelog.

Checklist:

  • The title of this PR complies with Conventional Commits.
  • I have edited the CHANGELOG accordingly.
  • I have made corresponding changes to the documentation.

@chenyan-dfinity chenyan-dfinity requested a review from a team as a code owner September 8, 2023 02:12
src/dfx/src/lib/operations/canister/motoko_playground.rs Outdated Show resolved Hide resolved

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 {

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?

Copy link
Contributor Author

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.

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!

@mergify mergify bot merged commit 9e74a14 into master Sep 15, 2023
172 checks passed
@mergify mergify bot deleted the playground-origin branch September 15, 2023 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants