Skip to content

RM-287: Add Text Display - #152

Merged
biast12 merged 5 commits into
masterfrom
RM-287
Oct 8, 2026
Merged

biast12 merged 5 commits into
masterfrom
RM-287

Conversation

@biast12

@biast12 biast12 commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

RM-287

Description

Adds Text Display (type 10) as a form field type.

Backend:

  • Accepts type 10 with content: required, at most 4,000 characters, and at most 4,000 in total per form.
  • Settings that don't apply to a field's type are cleared before validation. Text Display drops label, placeholder, description and required; other types drop content.
  • A field's options and API config are cleaned up according to its type, inside the save transaction. This also stops leftover options and API configs from staying behind after a type change.
  • Removes an existing connection-pool deadlock risk: options were read outside the save transaction.
  • Gallery snapshots and imports carry content.

Frontend:

  • "Text Display" type with a Content box and live preview. Settings that don't apply are hidden.
  • A warning when the combined length is too long, and a note when every field is a Text Display.
  • Clone, the setup wizard and the gallery preview handle content.

Included:
TicketsBot-cloud/worker#154
TicketsBot-cloud/docs#43

Needs: TicketsBot-cloud/database#45

Type of Change

  • Bug fix
  • New feature
  • Breaking change

Testing

Make a form with only a Text Display, and open a ticket with it, not form output should show in the ticket as no inputs are added
Add another type to the form, and open a new ticket (and add something to the input), you should see the output for that that 1 input type

Checklist

  • My code follows the style of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works

Support Text Display fields with Discord markdown content, validation, previews, gallery snapshots, and a 4000-character total limit across backend and frontend form management.
@tailwindcss/node 4.3.0 called module.register() on load, which Node 26
flags as deprecated (DEP0205) on every vite dev/build run. 4.3.3 uses
module.registerHooks() when available (tailwindlabs/tailwindcss#19907).

Bumps tailwindcss and @tailwindcss/vite from ^4.2.1 to ^4.3.3. Lockfile
changes are limited to Tailwind packages.
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 23, 2026 •

Copy link
Copy Markdown

Deploying tickets-v2-dashboard with  Cloudflare Pages  Cloudflare Pages

Latest commit: b817e8e
Status: ✅  Deploy successful!
Preview URL: https://d2d44731.tickets-v2-dashboard.pages.dev
Branch Preview URL: https://rm-287.tickets-v2-dashboard.pages.dev

View logs

Configure Vite's development server to open the resolved base URL instead of always opening the root page.
@BenHall-1

Copy link
Copy Markdown
Member

Ready for bump!

@biast12

biast12 commented Oct 2, 2026

Copy link
Copy Markdown
Contributor Author

@BenHall-1 Bumped!!

@biast12
biast12 merged commit f0236a4 into master Oct 8, 2026
2 checks passed
@biast12
biast12 deleted the RM-287 branch October 8, 2026 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type:feature New Feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants