Developer Journey Level 3: Space Engineer

[jessiemongeon1]

Level 3: Space engineer

• 3.1: Motoko package managers

  • What is a package manager?
  • Installing Mops.
  • Installing Vessel.
  • Using Mops.
    • Creating a new project.
    • Configuring your project to use Mops.
    • Initializing Mops.
    • Adding packages to mops.toml.
  • Publishing a package.
  • Using Vessel.
  • Importing packages into your Motoko code.

• 3.2: Using HTTPS outcalls.

  • Supported HTTPS methods.
  • Cycles.
  • HTTPS outcalls API.
  • HTTPS GET.
    • Prerequisites.
    • Creating a new project.
    • Creating an HTTP GET request.
    • Calling the HTTP GET request.
  • HTTPS POST.
    • Prerequisites.
    • Creating a new project.
    • Creating an HTTP POST request.
    • Calling the HTTP POST request.

• 3.3: Certified data.

  • How data is certified.
    • Data certificates.
    • How canisters certify data.
    • Certified data API methods.
  • How Developers can certify data.
    • Certified data Motoko module.
    • Certified data Rusk CDK module.
  • Generating an HTTPS response.
    • Example.
  • Using certified variables.
    • Prerequisites.
    • Creating a new project.
    • Creating an HTTP request.
    • Interacting with certified variables.
  • Resources.

• 3.4: Introduction to agents.

  • What does an agent do?
    • Structuring data.
    • Decoding data.
    • Managing authentication.
      • Accepted identities.
  • Available agents.
  • Using the JavaScript agent.
    • Prerequisites.
    • Creating a new project.
    • Generating Candid declarations.
    • Creating the JavaScript agent.
    • Using the agent.

• 3.5: Identities and authentication.

  • Types of identity.
  • Internet Identity.
    • Internet Identity architecture.
    • What is a passkey?
  • Creating an Internet Identity.
  • Integrating an Internet Identity into your app.
    • Prerequisites.
    • Creating a new project.
    • Creating an actor.
    • Importing the auth-client package.
    • Pulling the Internet Identity canister.
    • Interacting with the integration.

• 3.6: Motoko level 3.

  • Principals and caller identification.
  • Adding access control with identities.
    • Prerequisites.
    • Creating a new project.
    • Creating an owner identity.
    • Writing backend code with access control.
    • Interacting with the dapp.
  • Pattern matching.
  • Periodic timers.

Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

• You have updated the .github/CODEOWNERS file according to your changes.
• You have registered new documents to /sidebars.js if any.

[ghost]

great work Jessie! the series is coming together very nicely 👍

[domwoe]

Hey @jessiemongeon1,

great progress!

I'm just starting to go through and I'm not sure if I find the time to review completely today (and I'm on vacation next week)
My main feedback for the HTTPS Outcalls section would be to stress some points a bit more

• Please discuss the transform function a bit more. This is often a source of frustration for people. When working locally, the transform function doesn't really matter much, since there's only one node making the call. Then later, when people deploy to the IC they often get an error because not all replicas get the same response (Not sure what's the acutal error, but would be good to show it)
• The max_response_bytes setting is often ignored by devs, but they can save a lot of cycles by setting appropriatly
• The final source of frustration when deploying to the IC is that you can only make HTTPS outcalls to APIs that support IPv6. You can check if an API supports IPv6 by using services like: https://ready.chair6.net/