The repo moves to git.stroblme.de:Fluksio/app.git and its sibling to Fluksio/index.git, so every cross-repo path reference moves with it. The architecture sources the roadmap cites now live in the docs repo under architecture/, and the brand marks in the index repo's src/assets. Also replaces the placeholder README with one that reflects the actual layout. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
38 lines
2.6 KiB
Markdown
38 lines
2.6 KiB
Markdown
This file captures tasks which derive from roadmap tasks (unfinished, deferred), bugs encountered during usage and feature requests/improvements which are not fitting directly in the roadmap.
|
|
Always sort by priority and put tasks blocked by other tasks/features at the dedicated section.
|
|
When working on a task, check for other, similar tasks that could be resolved on the way.
|
|
Use following pattern to classify tasks: TYPE/SCOPE
|
|
Where TYPE could be BUG, FEAT, PERF, CHORE and SCOPE could be UX, UI, FLOW, NODE, API, INFRA, DOCS appended by MOBILE if only for mobile use case.
|
|
Don't write temporary reasons for deferring a task in the task description (only strategical reasons should be noted).
|
|
Deferring because out of scope is fine, but don't mention deferring than.
|
|
|
|
## Open
|
|
|
|
- CHORE/FLOW: `backend/app/flow/` is not an importable package. There is no `__init__.py`
|
|
and siblings are imported top-level (`from util import …` in `nodes.py:6`, `from nodes
|
|
import …` in `controller.py:23-26` and `pipeline.py:17-19`), so the modules only run with
|
|
the cwd set to `app/flow/`. Convert to `from app.flow.util import …`.
|
|
- CHORE/FLOW: the flow test files live in `backend/app/flow/test*.py`, inside the package
|
|
rather than `backend/tests/`, so `coverage run -m pytest tests/` never collects them.
|
|
- CHORE/INFRA: port the n3xd CI workflows (pre-commit, backend tests, Playwright shards,
|
|
compose smoke) to `.gitea/workflows/`. The Gitea instance runs Gitea Actions and needs CI
|
|
enabled per repository.
|
|
- FEAT/UI: `@xyflow/react` and a Monaco editor belong here once the node canvas starts.
|
|
The website already demos `@xyflow/react` on its features page.
|
|
- FEAT/UI: reintroduce `--chart-*` tokens as one designed sequential scale when the first
|
|
chart lands. The stock shadcn five were dropped because their light and dark values are
|
|
unrelated hues.
|
|
- CHORE/API: `backend/app/models.py` still holds only the template's `User` and `Item`.
|
|
`Item` should go once flow persistence replaces it.
|
|
- PERF/UI: both frontend bundles exceed the 500 kB warning threshold. Revisit chunking
|
|
once the canvas and editor are in, since they will dominate.
|
|
|
|
## Blocked
|
|
|
|
- FEAT/INFRA: Redis, MQTT broker and InfluxDB compose services. Blocked on the flow engine
|
|
being reachable from the API — no runtime path imports them today.
|
|
- CHORE/INFRA: `bun install` inside the frontend Docker build intermittently fails with
|
|
"Fail extracting tarball" for several packages at once, and succeeds on a plain rebuild.
|
|
It looks like concurrent extraction under memory pressure. Pin down or retry in the
|
|
Dockerfile if it starts costing CI time.
|