feat(tenant): add description template field to tenant settings#1564
Open
jeffreyvdhondel wants to merge 1 commit into
Open
feat(tenant): add description template field to tenant settings#1564jeffreyvdhondel wants to merge 1 commit into
jeffreyvdhondel wants to merge 1 commit into
Conversation
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.
What & why
Adds an optional, per-tenant Idea Template that prefills the description editor when a user opens the "Share your idea" modal. Admins configure a structured template (e.g. What is your idea? / What problem does
it solve? / Who benefits?) so submissions arrive with consistent, useful detail instead of a blank box.
The setting follows the same pattern as the existing
WelcomeMessage/Invitationtenant fields, so it slots into the current architecture with no new concepts.Behaviour
Changes
Backend :
202606081200_add_tenant_description_template.sqladdstenants.description_template TEXT NOT NULL DEFAULT ''description_templatethreaded through the tenant entity, DB scan struct +ToModel, the two tenantSELECTs, the settingsUPDATE, theUpdateTenantSettingscommand/action (incl. a 2000-char validation), andthe admin handler
Frontend:
descriptionTemplateadded to theTenantmodel and the update-settings request payloadShareFeedback.tsxprefills the editor from the tenant template when no draft existsNotes
'', so existing tenants behave exactly as before until they opt in.