Spacialist Documentation
Home
User
Developer
GitHub
Home
User
Developer
GitHub
  • User

    • Overview
    • Getting Started
    • Dictionary (Thesaurus)
    • User And Role Management
    • Data Model
      • Entity Type
      • Attribute
      • Attribute Types
    • Entity
    • Collaboration
    • Bibliography
    • Spatial Data
    • Data Importer
    • Data Analysis Tool
  • Developer

    • Developer
    • Environment
    • Coding Structure
    • Plugin
    • Classes

      • Entity Type
    • Commands

      • Export Entity Types (Data Model)
      • Refresh Testing
    • Common Issues

Coding Structure

Blank diagram

Components <> Store <> Api

Since we moved to Pinia in v.0.11.0 we want to focus on the dataflow always moving through the store. When components need some data, they should always request the data from the store. The store on the otherhand can then decide how to act on those requests. He can serve the cached files directly or fetch new data from the server, using the api.js script. This workflow should be used, unless we need 'stateless' requests from the components, e.g. we have a multiselect field, that wants to show a list of results.

Edit this page
Last Updated: 8/8/25, 6:15 PM
Contributors: Severino
Prev
Environment
Next
Plugin