nofusscomputing / nofusscomputing/centurion_ui

Backend Driven app setup

Open
#217 0 comments 0 reactions 1 assignee View on GitHub

@jon-nfc is already working on this.

Since Aug 11, 2026.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
1d 4h
Merged PRs (30d)
20

Description

Summary

The backend is required to setup the frontend ready for usage.

Description

The UI is not-functional on its own. The app (UI) needs to be setup and since the intent is that the UI be dynamic. The backend needs to supply this information.

The app is considered setup, when the routes, navigation and UI feature information has been obtained from the backend leaving the UI then to fetch what is required to display a dataset or single row of a dataset.

Business Value / Objectives
  • Improve app loading
  • Make dynamic. No backend, frontend remains non-functional.
  • Improve UX
Success Criteria
  • Routes are fetched from backend with UI creating routes
  • Navigation is fetched from backend with UI rendering navigation
  • UI Feature Settings fetched from backend with UI rendering (toolbar icon)
  • UI Feature Notifications fetched from backen with UI rendering (toolbar icon)
    If backend does not support notification, alerts must still function (i.e. the popup)
  • Skeletons are used when loading
  • Error Boundary added within view to capture HTTP/4xx
  • Backend Provider is the only location for backend data
Scope

The following of the app loading:


APP Load --> fetch routes / navigation --o-- render routes ---------+
                                          \                         +------------- Ready to render view
                                            o-- render navigation --+

Scope is anything before Ready to render view

Dependencies

No response

Risks & Mitigations
  • Data passed to UI from backend not sanitised
    Risk: Potential for XSS.
    Mitigation: Sanitize all backend data.
Stakeholders / Roles
  • developers
Milestones / Timeline
  1. Backend provided navigation and routes
  2. Backend provided UI feature setup
Linked Features / Stories (Task List)
  • App Setup Object
    A class / hook that is used as a single object that contains the complete object. ???
    • Capture 401 in root route ErrorBoundry
    • require backend login url
    • require backend logout url
  • Backend routes spec
  • Backend navigation spec
  • Backend Features spec
  • #121
  • #214
Additional Notes / References

Even though all of these "features" are separate, All data should come from a single endpoint. Possibly the API root Options endpoint.

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.