• Sns.Admin
  • /docs/developer/state-patterns
  • Docs
    • Overview
      • Approach
      • Vision
    • Concepts
      • Communities
      • Places
      • Structures
      • Spaces
      • Assets
    • Platform
      • Architecture
      • Sns.Framework
      • Sns.Spatial
      • Data Model
    • UX Patterns
      • Entity Icons
      • Editors
      • Layouts
      • Navigation
    • Workflows
      • Place Onboarding
      • Asset Uploads
      • Requests
      • Projects
    • Spatial
      • Maps
      • Providers
      • Geo DTOs
      • Digital Twins
    • Data
      • Places
      • Assets
      • NavItems
      • Scoring
    • AI / Automation
      • AI Assistants
      • Completeness
      • Confidence
      • Monitoring
    • Developer Guide
      • Getting Started
      • Repo Map
      • State Patterns
      • Coding Standards

New Page

docs/developer/state-patterns

State Patterns

SnS uses scoped state services to coordinate UI, data loading, selection, filtering, and feature workflow state. The dominant pattern builds on DataMine.Framework StateBase-style services and OnChanged notifications.

Common Responsibilities

  • Track loading, readiness, dirty state, errors, and update timing.
  • Resolve current selections and selected record IDs.
  • Coordinate list filters, search text, active views, and active-class helpers.
  • Notify subscribed components through OnChanged.
  • Keep persistence in services rather than Razor components.

Component Pattern

Components subscribe to the feature state, call StateHasChanged when notified, and unsubscribe during disposal. Layouts often initialize state early so child components can render from a ready state.

More info goes here.
  • Home
  • Finder
  • This Place
  • Explore
  • Database
  • Solutions
  • Ready
  • : 1
  • Enterprise: 13
  • Application: 1046
  • NavItem:
  • Theme: 1