Skip to content

Conversation

@jasonz-dfinity
Copy link
Contributor

Use a new variant Bool rather than Nat(1)/Nat(0). This is more intuitive and more readable than Nat.

@jasonz-dfinity jasonz-dfinity requested a review from a team as a code owner January 14, 2026 22:56
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This pull request changes code owned by the Governance team. Therefore, make sure that
you have considered the following (for Governance-owned code):

  1. Update unreleased_changelog.md (if there are behavior changes, even if they are
    non-breaking).

  2. Are there BREAKING changes?

  3. Is a data migration needed?

  4. Security review?

How to Satisfy This Automatic Review

  1. Go to the bottom of the pull request page.

  2. Look for where it says this bot is requesting changes.

  3. Click the three dots to the right.

  4. Select "Dismiss review".

  5. In the text entry box, respond to each of the numbered items in the previous
    section, declare one of the following:

  • Done.

  • $REASON_WHY_NO_NEED. E.g. for unreleased_changelog.md, "No
    canister behavior changes.", or for item 2, "Existing APIs
    behave as before.".

Brief Guide to "Externally Visible" Changes

"Externally visible behavior change" is very often due to some NEW canister API.

Changes to EXISTING APIs are more likely to be "breaking".

If these changes are breaking, make sure that clients know how to migrate, how to
maintain their continuity of operations.

If your changes are behind a feature flag, then, do NOT add entrie(s) to
unreleased_changelog.md in this PR! But rather, add entrie(s) later, in the PR
that enables these changes in production.

Reference(s)

For a more comprehensive checklist, see here.

GOVERNANCE_CHECKLIST_REMINDER_DEDUP

@github-actions github-actions bot added the feat label Jan 14, 2026
@jasonz-dfinity jasonz-dfinity force-pushed the jason/misc-self-describing-bool branch from 73558ad to 4eec373 Compare January 20, 2026 22:31
Base automatically changed from jason/misc-self-describing-tests to master January 20, 2026 23:15
@jasonz-dfinity jasonz-dfinity force-pushed the jason/misc-self-describing-bool branch from 4eec373 to abe722f Compare January 20, 2026 23:42
@jasonz-dfinity jasonz-dfinity dismissed github-actions[bot]’s stale review January 20, 2026 23:44

N/A - behind feature flag

@jasonz-dfinity jasonz-dfinity added this pull request to the merge queue Jan 21, 2026
Merged via the queue into master with commit 9664efe Jan 21, 2026
63 of 64 checks passed
@jasonz-dfinity jasonz-dfinity deleted the jason/misc-self-describing-bool branch January 21, 2026 00:50
github-merge-queue bot pushed a commit that referenced this pull request Jan 21, 2026
…_value (#8437)

Recent changes #8205 and #8366 added support for
SelfDescribingValue::[Bool|Null], while
`decode_candid_args_to_self_describing_value` was still using `Nat` for
booleans and empty arrays for nulls. This PR make
`decode_candid_args_to_self_describing_value` consistent with the rest
of the action-based proposals.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants