Skip to content

PRESIDECMS-2906 Client side validation defensive when validator didnt have client side defined#1554

Open
teonator wants to merge 2 commits intostablefrom
feature-PRESIDECMS-2906_client-side-validation-defensive-when-validator-didnt-have-client-side-defined
Open

PRESIDECMS-2906 Client side validation defensive when validator didnt have client side defined#1554
teonator wants to merge 2 commits intostablefrom
feature-PRESIDECMS-2906_client-side-validation-defensive-when-validator-didnt-have-client-side-defined

Conversation

@teonator
Copy link
Contributor

No description provided.

@github-actions
Copy link

github-actions bot commented Dec 16, 2024

Test Results

    1 files  ±0    109 suites  ±0   2m 28s ⏱️ -1s
1 734 tests ±0  1 731 ✅ ±0  3 💤 ±0  0 ❌ ±0 
1 737 runs  ±0  1 734 ✅ ±0  3 💤 ±0  0 ❌ ±0 

Results for commit f73cbf6. ± Comparison against base commit 492f770.

♻️ This comment has been updated with latest results.

</cfif>

<cfif Len( Trim( formId ) ) and Len( Trim( validationJs ))>
<cfset event.include( assetId="/js/frontend/formbuilder/" )>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little sceptical of this. We're making a dependency on form builder frontend features whereas this layout is for the general preside forms system and is used in both admin and frontend non-formbuilder forms. I feel this logic could/should go somewhere else perhaps?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants