FEATURE: support to initial values for form templates through /new-topic #23313
Conversation
This file contains 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
renato
force-pushed
the
form_template_initial_values
branch
from
5bcea6c
to
74c34c3
Compare
keegangeorge
approved these changes
Aug 29, 2023
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.
Adds support to setting initial values for the (experimental) form templates through
/new-topic?fieldname=fieldvalue.A new required
idfield was also added to the form template fields to support both this/new-topicapproach without relying on the field Label as well as the future implementation of the JSON output that will be stored with the created topic.Default
max_form_template_content_lengthwas bumped to 5k as the old default was not enough for our initially tested use cases.