Settings validation for includes fails.

Created on 9 March 2023, about 2 years ago
Updated 17 March 2023, about 2 years ago

Problem/Motivation

There is currently validation for the jsonapi includes fields in the settings form that is not validating correctly resulting in the inability to submit the form for valid includes. We are already validating includes again before they get submitted in api request (which is working fine) so this additional check was just a nice to have. Ultimately, we can remove this validation and let the user(s) be responsible for ensuring they have entered field names correctly.

Steps to reproduce

Add chained includes like field_components.field_media.field_image for multiple types, verify those are actually valid includes but the form thinks they're not.

Proposed resolution

Remove validation logic from settings form.

πŸ› Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States apmsooner

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024