HOME DOCS ABOUT
Discord
  1. Replicator
    1. Write
    2. Read
    3. Upgrading the Container
  2. Concepts
    1. Storing Information
    2. Writing Specifications
    3. Projecting Results
  3. Modeling
    1. Setting Up your Notebook
    2. Top-Level Facts
      1. Log In
      2. Save Facts
      3. Query for Successors
    3. Entities
      1. Deleting Facts
      2. Restoring Facts
      3. Mutable Properties
      4. Conflicts
      5. Projections
      6. Additional Mutable Properties
    4. Hierarchy
      1. Child Objects
      2. Tree View
    5. Workflow
      1. Steps
      2. Captured Versions
      3. Additional Workflow Steps
  4. LINQ Guidance
    1. Defining a Starting Point
    2. Tracing a Path
    3. Excluding Facts
    4. Selecting Projections
    5. Encapsulating Specifications
    6. Syntax Alternatives
    7. Limitations
  5. Building Applications
    1. Install Packages
    2. Define Settings
    3. Configure Jinaga
    4. Define a Model
    5. Save Facts
    6. Query Facts
    7. Create a View Model
    8. Control View Model Lifetime
    9. Load User Data
    10. Indicate App State
    11. Define Authorization Rules
    12. Define Distribution Rules
  6. Reference
    1. JinagaClient
    2. IObserver
    3. JinagaClientOptions
    4. IHttpAuthenticationProvider
    5. JinagaStatus
  1. Modeling
  2. Top-Level Facts

Log In

The user is the starting point of the model. You'll need to call Login to get the logged in user.

// Login returns the user fact and profile information
var (user, profile) = await jinagaClient.Login();

In your Notebook, you can call the jinagaClient.RenderFacts method (without a semicolon) to output a graph of facts. Give that a try with the user.

// Call RenderFacts on the Jinaga client to display the facts
jinagaClient.RenderFacts(user)

This will produce the following graph:

%0 eLG0D2gojV+51Ix80JNo2Uh4EQTKvjbZUq5JNrf9K5gSXEqRmi7LBSleOl09F/bWdrlWUgDkalEH847v83U7fA== Jinaga.User publicKey --- FAKE USER ---

When you are modeling, you are using the JinagaTest client factory, which is intended for unit tests. This factory lets you specify a user to simulate being logged in. That is the user fact that is returned to you.

In a real application, the User fact will represent an authenticated user. The means of authentication is based on your configuration. For example, for a MAUI application, you might authenticate with the user's Apple ID or Google ID. That will produce a User that is unique to them. Authorization and distribution rules govern which users are allowed to write and read which facts.

Continue With

Save Facts

Jinaga is a product of Jinaga LLC.

Michael L Perry, President