@micromerce/formbuilder-react 1.0.1014 → 1.0.1016
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/components/controls/SubtypeInput/SubtypeInput.d.ts +3 -1
- package/dist/components/controls/SubtypeInput/stories/subtypeStory.d.ts +8 -0
- package/dist/components/groups/PaymentGroup/PaymentGroup.d.ts +22 -0
- package/dist/formbuilder.js +52 -52
- package/dist/formbuilder.js.map +1 -1
- package/dist/index.d.ts +6 -2
- package/dist/utils/payment/index.d.ts +89 -0
- package/package.json +1 -1
|
@@ -15,7 +15,9 @@ export declare const isCheckedSubtype: (customAttributes: unknown) => boolean;
|
|
|
15
15
|
* A failing value is not this control's business: the submit goes to the server, which refuses it and
|
|
16
16
|
* sends the reason, localized, back to the field (like every other field error). The editor never
|
|
17
17
|
* blocks a submit, so it can never be stricter than the server. The input keeps its `type` and gets
|
|
18
|
-
*
|
|
18
|
+
* no `pattern` here: FormBuilder runs checkValidity() before every submit, so a pattern would make the
|
|
19
|
+
* editor block values the server accepts. The pattern is for the server-rendered HTML form (README,
|
|
20
|
+
* "HTML compatibility").
|
|
19
21
|
*/
|
|
20
22
|
declare const SubtypeInput: (props: InputProps) => React.JSX.Element;
|
|
21
23
|
export default SubtypeInput;
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
import type { StoryObj } from "@storybook/react-webpack5";
|
|
2
|
+
/** One field with a subtype, in a FormBuilder of its own (the form's theme and type face, as in the app). */
|
|
3
|
+
export declare const field: (displayName: string, customAttributes: Record<string, unknown>, value?: string, type?: string) => StoryObj;
|
|
4
|
+
export declare const parameters: {
|
|
5
|
+
controls: {
|
|
6
|
+
disableSaveFromUI: boolean;
|
|
7
|
+
};
|
|
8
|
+
};
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
import React from "react";
|
|
2
|
+
import type { controlProps } from "../../../types/controlProps";
|
|
3
|
+
import { GroupFormControl } from "../../../types";
|
|
4
|
+
export interface IProps {
|
|
5
|
+
id: string;
|
|
6
|
+
control: GroupFormControl;
|
|
7
|
+
objectPathId?: string;
|
|
8
|
+
groupIsRequired?: boolean;
|
|
9
|
+
isInRequiredGroup?: boolean;
|
|
10
|
+
isInGroup?: boolean;
|
|
11
|
+
controlProps?: controlProps;
|
|
12
|
+
helper?: string;
|
|
13
|
+
}
|
|
14
|
+
/**
|
|
15
|
+
* The payment of an invoice as one block (`custom-attributes.type: "payment"` on a group, COP-4613): due
|
|
16
|
+
* date, payment date and method side by side, the linked transactions below, any other child on a row of
|
|
17
|
+
* its own. Each field keeps its name as a small caption above it (a date input shows no placeholder). The
|
|
18
|
+
* group only lays out its fields; the state (paid, open, overdue, paid without a linked transaction) is
|
|
19
|
+
* shown by service-entity's detail view, which reads the same roles.
|
|
20
|
+
*/
|
|
21
|
+
declare const PaymentGroup: ({ id, control, objectPathId, groupIsRequired, isInRequiredGroup, isInGroup, controlProps, helper, }: IProps) => React.JSX.Element;
|
|
22
|
+
export default PaymentGroup;
|