OpenFn / OpenFn/lightning

Seed sandboxes in setup_demo so the sandbox UX is demonstrable out of the box

Open
#4,774 0 comments 0 reactions 1 assignee View on GitHub

@elias-ba is already working on this.

Since Jun 4, 2026.

Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

Problem

Lightning.SetupUtils.setup_demo/1 seeds two demo projects (OpenHIE and DHIS2) but no sandboxes. Anyone walking through the sandbox feature on a fresh demo instance has to provision them by hand to see the UI in a realistic state.

Suggested fix

Have setup_demo also provision three sandboxes after the projects are created:

  • openhie-dev under OpenHIE (created by Amy as admin; all four demo users inherit because they're all on OpenHIE).
  • dhis2-dev under DHIS2 (created by Amy as owner; only Amy is on DHIS2, so the sandbox starts with just her).
  • dhis2-feature-x nested under dhis2-dev (demonstrates the nesting feature, the breadcrumb truncation, and the picker collapsing hidden ancestors).

That gives a demo state where Sizwe naturally cannot see anything under DHIS2 (the visibility filter in action) while still being able to demo OpenHIE and its sandbox. Useful for clicking through the sandbox docs without any extra setup.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.