Fluksio/app
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
9cede8dbb5171bb27734b932827b3ae3af8d2317
app/NOTEPAD.md
T
Melvin StroblandClaude Fable 5 aa0e760615 Give the pulse its own duration, and let the editor fill the screen 
The shared duration tokens had been stretched to slow the pulses down, which
also slowed every panel and dock animation and left `motion.ts` out of step
with the CSS. Both are back to 200/300 ms, and the pulses use a new
`--duration-pulse` (500 ms): a message arriving is a signal, not a state
change, and it is the only thing here that should linger. The edge pulse read
its own 300 ms constant, so it now takes the token through `motion.ts` and the
two sides cannot drift again.

The code editor also expands: the same node panel fills the content region
beside the sidebar, the canvas chrome steps aside rather than floating on top,
and the settings above the editor keep a readable width.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016WzrvW7rjQbynnhF6pxh6i
2026-08-15 20:03:21 +02:00

4.8 KiB
Raw Blame History

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

  • BUG/UI: the sidebar background on dark mode does not match the background of the viewport/flow panel
  • BUG/UI: there is some strage dot (li item) sitting next to the appearance button
  • FEAT/UI: introduce User settings page showing up in the sidebar where the apperance, email password etc can be set (copy UX design from ../../n3xd/app)
  • BUG/UI: edge value labels should be opaque
  • BUG/UI: the popover which opens when clicking on an edge should be more compact, i.e. make label, value and last updated fit in a single row (truncate decimals)
  • BUG/API: pytest tests/ deletes every user on teardown (tests/conftest.py), so running it against the development database logs you out of the running app. Point tests at their own database, or reseed with init_db afterwards.
  • CHORE/FLOW: the InfluxDB token committed in the old flow/nodes/influx_test.py is in pushed history (d222ce5). Rotate it in InfluxDB; removing it from history needs a rewrite of published commits.
  • BUG/UI: six template Playwright specs fail on validation copy that no longer matches (login, sign-up, reset-password, user-settings theme persistence). Unrelated to the flow editor, which passes; fix or delete them with the Item cleanup.
  • CHORE/UI: bunx playwright test starts a dev server on :5173, which is not in the API's BACKEND_CORS_ORIGINS, so every spec fails at login. Run against the integrated stack with PLAYWRIGHT_BASE_URL=http://app.localhost, or add the dev origin to CORS.
  • FEAT/UI: no undo on the canvas. Deleting a node autosaves immediately, so a mis-click costs the node's source.
  • PERF/UI: the Monaco chunk is 2.6 MB. It only loads when a node panel opens, but the editor could be trimmed further or swapped for CodeMirror if that becomes a problem.
  • FEAT/UI: renaming a message updates only the node being edited; the nodes consuming it keep the old name and quietly disconnect. Offer to rename across the flow.
  • 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.
  • CHORE/FLOW: app/flow/nodes.py and state.py are excluded from strict mypy ([[tool.mypy.overrides]] in pyproject.toml). The node classes still carry prototype typing and redis-py types its calls as sync/async unions. Shrink the exclusion as each integration is revisited.
  • FEAT/API: per-hook shared secrets for HttpNode webhooks. They are mounted unauthenticated under /hooks/{flow}/… because devices cannot present a JWT.
  • FEAT/FLOW: state does not survive a restart — the engine runs on MemoryState unless REDIS_HOST is set, and there is no Redis compose service yet.
  • CHORE/FLOW: rotating SECRET_KEY makes the stored secrets unreadable, since the Fernet key is derived from it. Needs a re-encrypt path before anyone rotates in production.
  • PERF/FLOW: every save rebuilds the whole pipeline. Fine at the current flow count; rebuild only the touched flow when it starts to show.
  • 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 the template's Item model. It has no purpose now that flows are persisted and can go with its routes and tests.
  • 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: MQTT broker and InfluxDB compose services for local development. The node types exist; a local broker would make them testable without external hardware.
  • 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.
Reference in New Issue View Git Blame Copy Permalink