Make domain package own traceroute statuses #80

New issue

Closed

opened 2026-02-14 21:54:18 +03:00 by skobkin · 1 comment

skobkin commented 2026-02-14 21:54:18 +03:00

Owner

Copy link

Make domain package own traceroute statuses.

Refactoring is needed to avoid import cycle.

Make domain package own traceroute statuses. Refactoring is needed to avoid import cycle.

skobkin added the

research needed

label 2026-02-14 21:54:18 +03:00

skobkin self-assigned this 2026-02-14 21:54:18 +03:00

skobkin commented 2026-02-14 21:59:15 +03:00

Author

Owner

Copy link

1. Move bus/topic wiring out of internal/domain into app/adapter layer.
2. Keep domain package free of connectors imports.
3. Then move traceroute status type back into domain and have connectors depend on it.

1. Move bus/topic wiring out of internal/domain into app/adapter layer. 2. Keep domain package free of connectors imports. 3. Then move traceroute status type back into domain and have connectors depend on it.

skobkin referenced this issue from a commit 2026-02-14 22:03:57 +03:00

refactor: centralizing traceroute status constants (part of #80)

skobkin referenced this issue 2026-02-14 23:26:22 +03:00

UI update UX: notifications + relay-aware delivery indicators, with key chat title/service fixes #81

skobkin referenced this issue from a commit 2026-02-19 04:32:36 +03:00

refactor: eliminating excessive 'traceroute' package (closes #89, closes #80)

skobkin closed this issue 2026-02-19 04:56:47 +03:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

node_settings_finish

0.19.1

0.19.0

0.18.0

0.17.1

0.17.0

0.16.0

0.15.0

0.14.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

0.8.2

0.7.0

0.6.1

0.6.0

0.5.1

0.5.0

0.4.3

0.4.2

0.4.1

0.4.0

0.3.1

0.3.0

0.2.0

0.1.0

0.0.3

0.0.2

Labels

Clear labels   

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

help wanted

Need some help

  

question

More information is needed

  

research needed

To implement this properly, some research should be done first.

  

wontfix

This won't be fixed

No labels

bug

duplicate

enhancement

help wanted

question

research needed

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

skobkin

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

skobkin/meshgo#80

No description provided.