Meeting Records

2024/04/06

Widget API

• Realize in the form of Tauri plugin, start with a minimal demo.
• How do we restrict users' access only to these exposed API but not to our internal commands?
• Can we allow user to do something like import { ... } from "@deskulpt/api"? The final resolution would be to bind the API on the window global object.

Tests

• Romee: bundler.rs unit tests.
• Yao: config.rs unit test.
• Yao: commands.rs unit test (using Tauri test framework, in particular for our internal commands).
• Xinyu: Widget API (after the framework is established, unit test).

Discussion

• Do we want something like Docker to be able to test on other platforms?
  • Docker does not have GUI.
  • Use virtual machine to test different platforms (Romee and Frank will investigate).

Next steps

• Yao: Solve #6.
• Xinyu: Format the canvas window.
• Frank: Familiarize with React, try to write some simple widgets.
• Yao: Set up test and codecov GitHub workflows.
• Xinyu: Extend widget APIs.

2024/03/29

GitHub workflow

We use GitHub workflow for CI and better consistency. In particular:

• We use .github/workflows/build.yaml to test if Deskulpt can be built on Ubuntu/Mac/Windows (this currently does not provide the actual artifact).
• We use .github/workflows/lint-core.yaml to test if Deskulpt code pass linting checks.

Both of the above are done in two scenarios:

• push.branch: main, i.e., when someone pushes to main branch (most likely when a PR is merged into main)
• pull_request.branch: main, i.e., when someone commits to a pull request that is targeted towards main.  

Homework 5

We divide into two pairs to write unit tests for two components of Deskulpt:

• Yao & Romee: bundler
• Xinyu & Frank: widget manager

Earlier Meetings

Our earlier meeting records were held in Notion, but due to its storage limits we have migrated to GitHub wiki. You can check our earlier meeting records at this published Notion site.