Repository navigation
Conversation
Signed-off-by: Ben Hall <ben@tickets.bot>
BenHall-1
changed the title
Signed-off-by: Ben Hall <ben@tickets.bot>
Deploying tickets-v2-dashboard with
|
| Latest commit: |
c8ce20f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://acf690fa.tickets-v2-dashboard.pages.dev |
| Branch Preview URL: | https://msg-perf.tickets-v2-dashboard.pages.dev |
Signed-off-by: Ben Hall <ben@tickets.bot>
Treat panel colours as nullable so an explicit black colour is retained during Components V2 saves and omitted colours remain unchanged. Update classic conversion to omit null accent colours.
Preserve existing panel data during partial updates, gate new Components v2 usage by feature flags and premium status, and persist panel names and component trees reliably. Update dashboard labels, validation, previews, accessibility, and related API behavior.
Improve Components V2 validation, premium gating, message reposting, and empty-panel handling. Preserve stored panel data safely, reduce unnecessary component queries, enforce input limits, and enhance builder accessibility and error feedback.
Allow Components V2 panel messages to place the panel's own button within the component tree, resolving it at send time and updating validation, editor controls, previews, and component budgeting.
Increase the reserved component count for welcome forms from 5 to 6 across backend and frontend validation, and update boundary tests accordingly.
Render classic component titles as level-three headings when converting to Components V2.
Reuse the exported heading rule when splitting component content and render type 10 text display components with the appropriate text profile.
Count Unicode code points consistently in ticket and frontend inputs, reject null characters in close reasons, and improve heading parsing, Discord message memoization, panel labels, and Node.js CI versions.
Place the panel title field alongside classic panel properties and use it as the panel name placeholder/default guidance. Remove obsolete Components V2 feature-flag logic from both create and edit forms.
Clamp text inputs by code points without blocking deletions, and validate integration descriptions consistently. Also use panel display names in labels and errors and improve heading escaping.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Type of Change
Testing
Related docs PR
TicketsBot-cloud/docs#46
Feature flag
Checklist
Dependencies
TicketsBot-cloud/database#48