mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #1833] RFFSelectSearch fields do not show validation errors visually #965
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#965
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sk1tt1sh on GitHub (Oct 26, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1833
Description
I tested locally and updated src/components/forms/RFFComponents.js RFFSelectSearch from:
<div><CFormLabel/>...<RFFCFormFeedback meta={meta} /></div>to:
<div><CFormLabel/>...{meta.error && meta.touched && <span className="text-danger">{meta.error}</span>}</div>Tried again and red "Required" showed underneath the field.
Not working:

With my change:

Environment data
@github-actions[bot] commented on GitHub (Oct 26, 2023):
Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".
Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
@sk1tt1sh commented on GitHub (Oct 27, 2023):
I have updated to 4.5.0 frontend and backend, since submitting this issue and the behavior continues.
@sk1tt1sh commented on GitHub (Oct 27, 2023):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.