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

Enh: domain/ layer imports isar_community directly in 3 files — violates Clean Architecture rule

Closed
#163 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
dart, flutter
Domain
backend

Research direction

Start by reading the three named service/use-case files and the existing GanaRepository/GanaRepositoryImpl pattern. Run grep -rn "package:isar_community" lib/domain/ to confirm the violations. Done means Isar access in each file goes through a Domain repository interface implemented in lib/data/, and the grep finds no remaining Domain imports.

Written by the indexing model from the issue text.

Description

enhancement good first issue

"Domain layer... Has zero imports from isar_community, flutter, or any presentation package." Three existing files break this — the Domain layer
should only reach Isar through repository interfaces implemented in lib/data/, but these reach into Isar directly:

  • lib/domain/services/nip17_encryption_service.dart:4
  • lib/domain/services/marmot_transport_service.dart:3
  • lib/domain/usecases/dm_usecases.dart:3

Verify with:
grep -rn "package:isar_community" lib/domain/

This predates the recent Gana cloud-support work (that work was checked against this exact rule and introduced no new violations — see docs/AUDIT.md, 2026-08-11
entry). Not urgent, not touched mid-feature — flagging for a deliberate cleanup pass: each of these three needs its Isar access moved behind a repository interface
(Domain) + implementation (Data), following the pattern already used everywhere else in the codebase (e.g. GanaRepository/GanaRepositoryImpl).

Dominant language
Dart
Stars
2
Forks
2
Avg merge
19h 21m
Merged PRs (30d)
37

Getting set up

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 basictech01/uniun

All issues in basictech01/uniun

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.