Libraries tagged by conditional fields

emneslab/custom-meta-box-builder

1 Favers
0 Downloads

A modern WordPress meta box builder with 30+ field types, visual admin UI, nested groups, conditional logic, REST API, Gutenberg sidebar, and WP-CLI support.

Go to Download


chmielewskitomasz/validator

1 Favers
881 Downloads

Simple validation tool, allows you to validate both simple and nested structures, introduces conditional fields. All you need is here. Perfect for REST endpoint validation. No dependencies required.

Go to Download


bacao/laravel-admin-hasmany-extra

0 Favers
1 Downloads

Laravel-admin helpers for hasMany multiple image upload and nested conditional fields.

Go to Download


bigfork/silverstripe-create-test-user-form

0 Favers
6 Downloads

Creates a test user form with a mix a of conditional and required fields

Go to Download


creationx/cixformconditions

0 Favers
1 Downloads

Conditional visibility for TYPO3 form framework elements (show/hide a field or text depending on another field's value).

Go to Download


bank-io/bankio-sdk-php

1 Favers
106 Downloads

# Summary The **NextGenPSD2** *Framework Version 1.3.6* (with errata) offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGenPSD2 Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe and, aligned with the goals of the Euro Retail Payments Board, enables European banking customers to benefit from innovative products and services ('Banking as a Service') by granting TPPs safe and secure (authenticated and authorised) access to their bank accounts and financial data. The possible Approaches are: * Redirect SCA Approach * OAuth SCA Approach * Decoupled SCA Approach * Embedded SCA Approach without SCA method * Embedded SCA Approach with only one SCA method available * Embedded SCA Approach with Selection of a SCA method Not every message defined in this API definition is necessary for all approaches. Furthermore this API definition does not differ between methods which are mandatory, conditional, or optional. Therefore for a particular implementation of a Berlin Group PSD2 compliant API it is only necessary to support a certain subset of the methods defined in this API definition. **Please have a look at the implementation guidelines if you are not sure which message has to be used for the approach you are going to use.** ## Some General Remarks Related to this version of the OpenAPI Specification: * **This API definition is based on the Implementation Guidelines of the Berlin Group PSD2 API.** It is not a replacement in any sense. The main specification is (at the moment) always the Implementation Guidelines of the Berlin Group PSD2 API. * **This API definition contains the REST-API for requests from the PISP to the ASPSP.** * **This API definition contains the messages for all different approaches defined in the Implementation Guidelines.** * According to the OpenAPI-Specification [https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md] "If in is "header" and the name field is "Accept", "Content-Type" or "Authorization", the parameter definition SHALL be ignored." The element "Accept" will not be defined in this file at any place. The elements "Content-Type" and "Authorization" are implicitly defined by the OpenApi tags "content" and "security". * There are several predefined types which might occur in payment initiation messages, but are not used in the standard JSON messages in the Implementation Guidelines. Therefore they are not used in the corresponding messages in this file either. We added them for the convenience of the user. If there is a payment product, which needs these fields, one can easily use the predefined types. But the ASPSP need not to accept them in general. * **We omit the definition of all standard HTTP header elements (mandatory/optional/conditional) except they are mentioned in the Implementation Guidelines.** Therefore the implementer might add these in his own realisation of a PSD2 comlient API in addition to the elements defined in this file. ## General Remarks on Data Types The Berlin Group definition of UTF-8 strings in context of the PSD2 API has to support at least the following characters a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 / - ? : ( ) . , ' + Space

Go to Download


unclecheese/display-logic

76 Favers
1125071 Downloads

Allows assignment of conditions for display and hide of specific form fields based on client side behavior.

Go to Download


in2code/powermail_cond

12 Favers
599443 Downloads

Add conditions (via AJAX) to powermail forms for fields and pages

Go to Download


silverstripe/display-logic

75 Favers
322431 Downloads

Allows assignment of conditions for display and hide of specific form fields based on client side behavior.

Go to Download


terminal42/contao-conditionalformfields

21 Favers
74588 Downloads

conditionalformfields extension for Contao Open Source CMS; Display form fields based on conditionis!

Go to Download


rasteiner/k3-whenquery

66 Favers
21815 Downloads

Conditionally show fields and sections. Better.

Go to Download


sqltools/where

1 Favers
104670 Downloads

PHP7.1 Fluent, immutable SQL query builder. Connectionless, framework-agnostic, no dependency.

Go to Download


wapplersystems/form

6 Favers
83 Downloads

WapplerSystems fork of typo3/cms-form — extended backend editor (variants/conditions UI), additional events, cross-field validators (e.g. entropy spam filter).

Go to Download


wezlo/filament-record-watcher

2 Favers
262 Downloads

Subscribe to Eloquent records and receive in-panel Filament notifications when they change, with per-watch condition rules and field diffs.

Go to Download


craftconditions/conditions

12 Favers
1970 Downloads

conditions on fields

Go to Download


<< Previous Next >>