Skip to main content
Your workspace settings in XanoScript follow a basic structure:
  1. Optional Description: A brief description of your workspace, placed at the top preceded by a // for comments.
// This application is designed to help users track and manage their Xano backends. It allows for the recording of essential backend details, categorization, status tracking, and notes on the development modality used.
  1. Workspace Declaration: The workspace block defines the workspace name and contains settings and preferences.
// This application is designed to help users track and manage their Xano backends. It allows for the recording of essential backend details, categorization, status tracking, and notes on the development modality used.
workspace "Backend Management Application" {
    ...
}
  1. Acceptance of AI Terms: The acceptance object indicates whether the user has accepted AI terms of service, required to utilize the SQL assistant.
// This application is designed to help users track and manage their Xano backends. It allows for the recording of essential backend details, categorization, status tracking, and notes on the development modality used.
workspace "Backend Management Application" {
    acceptance = {ai_terms: false}
    ...
}
  1. Preferences: The preferences object contains various boolean settings that customize the workspace behavior.
// This application is designed to help users track and manage their Xano backends. It allows for the recording of essential backend details, categorization, status tracking, and notes on the development modality used.
workspace "Backend Management Application" {
  acceptance = {ai_terms: false}
  preferences = {
    internal_docs    : false
    track_performance: true
    sql_names        : false
    sql_columns      : true
  }
}
Setting NameDescriptionDefault Value
internal_docsEnables or disables internal documentation features.false
track_performanceTrack run times and counts of function stack runs to gather insights.true
sql_namesSet readable, custom names for SQL access instead of using default identifiers.false
sql_columnsNew tables will use individual SQL columns instead of a JSONB fieldtrue