Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: /demo notes app #3411

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

matijamarjanovic
Copy link
Contributor

WIP

Description

Notes is an application that alows gnomes to use the chain as their notepad. Each user can post notes using a transaction as well as from other realms (maybe have all thoughts in one place without having to leave comments intented only for the creator himself). It uses an avl.Tree as a map of address->Btree where the btrees aro user's notes collection. Notes also have 2 different "settings", either they are private or they are public, meaning that some notes of a user can be made to be visible by other poeple. I am currently looking into the implementation of namespaces as path parameters (not only addresses) but to my knoledge namespaces are currently being refactored.

Contributors checklist

  • make notes tree and system to add, get and delete notes
  • make a render function that displays user notes by taking the address path parameter
  • implement showing users notes with no path parameters (by using std.GetOrigCaller() if possible?)
  • implement private and public type of notes which checks who is the one reading them
  • add tests

@github-actions github-actions bot added the 🧾 package/realm Tag used for new Realms or Packages. label Dec 27, 2024
@Gno2D2
Copy link
Collaborator

Gno2D2 commented Dec 27, 2024

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):
  • IGNORE the bot requirements for this PR (force green CI check)
  • The pull request description provides enough details
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
└── 🟢 The pull request was created from a fork (head branch repo: matijamarjanovic/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
The pull request description provides enough details

If

🟢 Condition met
└── 🟢 Not (🔴 Pull request author is a member of the team: core-contributors)

Can be checked by

  • team core-contributors

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: Triage
Development

Successfully merging this pull request may close these issues.

2 participants