LetsFlow
  • Introduction
  • Tutorial
    • The basics
    • A handshake
    • A conversation
    • A proper introduction
    • Group meeting
  • Cookbook
  • ENGINE
    • Installation
    • Authentication
    • API
    • Services
      • ZeroMQ
      • AMQP 0-9-1
      • Webhook
      • Engine service
  • Integration
    • Frontend
      • React
      • Angular
      • Vue
      • Svelte
    • Backend
  • Reference
    • Scenario
      • Actor
      • Action
        • Update instruction
      • State
        • Transition
          • Log
        • Notify
      • Data functions
    • Schema
    • Process
      • Current state
      • Previous log
      • Prediction
      • Events
        • Instantiate event
        • Action event
        • Timeout event
  • Libraries
    • Core library
    • JMESPath
    • Test suite
  • Advanced topics
    • Deep integration
    • Distributed workflows
    • Custom JMESPath functions
    • Custom YAML tags
Powered by GitBook
On this page

Was this helpful?

  1. Libraries

Core library

PreviousTimeout eventNextJMESPath

Last updated 10 days ago

Was this helpful?

This page is a stub. More information will be provided

yarn add @letsflow/core

normalize

The normalized JSON is convenient for processing by a computer. But is very verbose and therefore less readable by humans.

Pretty JSON collapses arrays, maps where there is only one option and omits properties that have the default value. This improves readability for humans, but is more difficult for computers are the structure and data types differ based on the data.

The YAML format is similar to pretty JSON, with the addition of custom tags for data functions. YAML is the recommended format for defining scenarios.

LogoGitHub - letsflow/letsflow: Core library of the LetsFlow workflow engineGitHub