feat(examples): Datastore package p/jeronimoalbi/datastore

[jeronimoalbi]

The purpose of this package is to support a data store where multiple collection based storages could be defined.

Each named storage defines a collection of records where each record can optionally and by default have any number of user defined fields, which can be constrained to a pre defined set of fields by using a schema definition.

The implementation is a layer on top of p/moul/collection.

Example of datastore package usage:

package main

import (
	ds "gno.land/p/jeronimoalbi/datastore"
)

func main() {
	var db ds.Datastore

	// Define a unique case insensitive index for user emails
	emailIdx := ds.NewIndex("email", func(r ds.Record) string {
		return r.MustGet("email").(string)
	}).Unique().CaseInsensitive()

	// Create a new storage for user records
	storage := db.CreateStorage("users", ds.WithIndex(emailIdx))

	// Add a user with a single "email" field
	u := storage.NewRecord()
	u.Set("email", "foo@bar.com")

	// Save to assing user ID and update index(es)
	u.Save()
	println("Records =", storage.Size())

	// Find the user by email
	print("Search by Email ... ")
	record := storage.WithIndex("email").GetFirst("foo@bar.com")
	if record != nil {
		println("ID =", record.ID())
	}

	// Find user by ID
	print("Search by ID ... ")
	record = storage.GetFirst(u.Key())
	if record != nil {
		email := record.MustGet("email").(string)
		println("Email =", email)
	}

	// Delete the user from the storage and update index(es)
	storage.Delete(u.ID())
	println("Records =", storage.Size())
}

// Output:
// Records = 1
// Search by Email ... ID = 1
// Search by ID ... Email = "foo@bar.com"
// Records = 0

[Gno2D2]

🛠 PR Checks Summary

🔴 Pending initial approval by a review team member, or review from tech-staff

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):

🔴 Pending initial approval by a review team member, or review from tech-staff

☑️ 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:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Pending initial approval by a review team member, or review from tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Not (🔴 Pull request author is a member of the team: tech-staff)

Then

🔴 Requirement not satisfied
└── 🔴 If
    ├── 🔴 Condition
    │   └── 🔴 Or
    │       ├── 🔴 At least 1 user(s) of the organization reviewed the pull request (with state "APPROVED")
    │       ├── 🔴 At least 1 user(s) of the team tech-staff reviewed pull request
    │       └── 🔴 This pull request is a draft
    └── 🔴 Else
        └── 🔴 And
            ├── 🟢 This label is applied to pull request: review/triage-pending
            └── 🔴 On no 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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!