Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@sasa-tomic
Copy link
Member

@sasa-tomic sasa-tomic commented Oct 22, 2025

Motivation

  • Add safe defaults for RegistryCanisterInitPayload

Solution

  • Implement explicit Default for RegistryCanisterInitPayload
  • Add serde(default) on is_swapping_feature_enabled and the three Vec fields with helper functions.
  • Provide default_false and default_empty_vec helpers.

Details

  • Defaults align with current initialization: empty mutations, feature flag false, empty whitelists/subnets.
  • Changes are purely about deserialization safety; no runtime behavior changes otherwise.

### Motivation
- Remove derive(Default) to enable explicit per-field defaults for new init payload fields.

### Solution
- Add explicit Default for RegistryCanisterInitPayload.
- Add default_false() and default_empty_vec() helpers and apply serde(default) to new fields.
- Keep existing fields and behavior; initialization now explicit.

### Details
- This avoids unintended Default propagation and clarifies initial state.
- No runtime logic changes beyond initialization defaults.
@sasa-tomic sasa-tomic self-assigned this Oct 22, 2025
@github-actions github-actions bot added the feat label Oct 22, 2025
@sasa-tomic sasa-tomic marked this pull request as ready for review October 22, 2025 13:57
@sasa-tomic sasa-tomic requested a review from a team as a code owner October 22, 2025 13:57
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant