Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Optimize message data fetching

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
backend, databases

Research direction

Start by locating the repository interface and message model described in the issue, then trace how message fields are currently fetched and saved. Done means the interface supports omitting flags, content, and parts, returned objects are read-only, and callers can identify partial models; no specific files or tests are named.

Written by the indexing model from the issue text.

Description

In some cases, it is not necessary to fetch some message fields:

  • Flags
  • Content data (envelope, etc)
  • Parts data (may be quite big).

Repository interface should support such partial fetching. Returned objects should be read-only and cannot be saved.
It should be possible to tell that the model object is "partial".

Dominant language
Go
Stars
3
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from foxcpp/maddy-storage

All issues in foxcpp/maddy-storage

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.