Repository navigation
Bug Fix: Use Short Description in Error Messages for Composite Question Types - #473
Merged
Scullyon merged 2 commits intoOct 5, 2026
Conversation
… short description is available.
|
jbarnsley10
approved these changes
Oct 5, 2026
jbarnsley10
left a comment
Contributor
There was a problem hiding this comment.
LGTM - although it might have been cleaner to do the type fixes in a separate PR ;-)
Scullyon
deleted the
feat/DF-1401-error-message-should-use-short-description-for-date-questions
branch
October 5, 2026 15:07
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.



Jira ticket: https://eaflood.atlassian.net/browse/DF-1401
NOTE:
Type of change
Error messages should use short description for date and other composite questions, instead of the error title. Also, use
Checklist
README.mdanddocs/*(where appropriate, e.g. new features).npm run test).npm run lint).npm run format).