File

mod_adhoc_dataforms_demo/README.markdown @ 4515:2e33eeafe962

mod_muc_markers: Prevent any markers from reaching the archive, even if untracked Original intention was to leave alone things that this module isn't handling. However markers in archives are just problematic without more advanced logic about what is markable and what is not. It also requires a more advanced query in mod_muc_rai to determine the latest markable message instead of the latest archived message. I'd rather keep the "is archivable" and "is markable" definition the same for simplicity. I don't want to introduce yet another set of rules for no reason. No markers in MAM.
author Matthew Wild <mwild1@gmail.com>
date Mon, 22 Mar 2021 15:55:02 +0000
parent 3559:d56cb74a0db8
line wrap: on
line source

---
summary: 'Module for testing ad-hoc commands and dataforms rendering'
---

# Introduction

This module provides [Ad-Hoc commands][xep0050] for testing [data
form][xep0004] that includes all kinds of fields. It's meant to help
debug both Prosodys
[`util.dataforms`][doc:developers:util:dataforms] library and
clients, eg seeing how various field types are rendered.

# Configuration

Simply add it to [`modules_enabled`][doc:modules_enabled] like any
other module.

``` {.lua}
modules_enabled = {
    -- All your other modules etc
    "adhoc_dataforms_demo";
}
```

# Usage

In your Ad-Hoc capable client, first look for "Execute command". You
should see a form with various kinds of fields.

Dataforms Demo
:   A simple command that provides a dataform with every possible field
    type, suitable for testing rending of dataforms.

Multi-step command demo
:   A command that has multiple steps, suitable for testing back and
    forwards navigation.