Skip to content

Store refactor - generic resource pattern and normalized entity model #51

@bburda

Description

@bburda

Summary

Refactor the Zustand store to use a generic resource pattern and normalized entity model instead of per-resource-type fetch functions.


Proposed solution (optional)

  • Unified useResource(entityType, entityId, collection) instead of separate fetchConfigurations(), fetchOperations(), etc.
  • Normalized entity model where all entity types (areas, components, apps, functions) are treated uniformly
  • Capabilities-driven tab/resource availability - entity capabilities determine which tabs are shown
  • Unified caching and loading state management across all resource collections

Additional context (optional)

Independent architectural improvement - not blocking other feature work. New feature tabs can be added in current style first, then unified by this refactor.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions