Skip to content

WIP feat(boards2): protected functions for sub-realms#5037

Draft
jeronimoalbi wants to merge 4 commits intognolang:masterfrom
jeronimoalbi:feat/protected-functions
Draft

WIP feat(boards2): protected functions for sub-realms#5037
jeronimoalbi wants to merge 4 commits intognolang:masterfrom
jeronimoalbi:feat/protected-functions

Conversation

@jeronimoalbi
Copy link
Member

This PR aims to introduce public Boards2 realm functions that can only be called from boards sub realms.

This would be necessary to implement, or move, specific features to sub-realms under gno.land/r/gnoland/boards2 namespace.

These "protected" public functions would allow to implement data migration between Boards2 versions for example, or to add optional features that would require access to specific board data.

Moving or implementing new features as sub-realms would help keeping Boards2 realm leaner and would allow for a more "micro services" oriented approach for new features.

For now board instances can only be getted by Boards2 sub realms to
allow data migration or other specific features through sub realms.

Feeds should be implemented in a sub realm, which requires access to
boards data.
Renamed to `GetRealmPermissions`.

The iterator was intended for data migration but now it makes sense as a
namespaces protected public function.
@Gno2D2
Copy link
Collaborator

Gno2D2 commented Jan 9, 2026

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):
  • IGNORE the bot requirements for this PR (force green CI check)
Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)

☑️ Contributor Actions:
  1. Fix any issues flagged by automated checks.
  2. Follow the Contributor Checklist to ensure your PR is ready for review.
    • Add new tests, or document why they are unnecessary.
    • Provide clear examples/screenshots, if necessary.
    • Update documentation, if required.
    • Ensure no breaking changes, or include BREAKING CHANGE notes.
    • Link related issues/PRs, where applicable.
☑️ Reviewer Actions:
  1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.
📚 Resources:
Debug
Automated Checks
Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: jeronimoalbi/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Manual Checks
**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

  • Any user with comment edit permission

@jeronimoalbi
Copy link
Member Author

These protected functions would allow to finish implementing board feeds support.

They also would be helpful to have, for example, a specific sub-realm with public functions that would return readonly (wrapped) boards objects to allow better integration from third party realms, or external non web3 apps though JSON.

cc @jefft0

@jeronimoalbi
Copy link
Member Author

Something to have in mind is that each board is intended to work as an independent community managed by a DAO, which is important when board instances are potentially accesible by future sub-realms which could override it.

@codecov
Copy link

codecov bot commented Jan 9, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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

Labels

🧾 package/realm Tag used for new Realms or Packages.

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants