You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/sites/demos/pc/webdoc/envpreparation-open-en.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
-
##Environment Preparation
1
+
# Environment Preparation
2
2
3
3
TinyVue is a`Vue`UI component library, which can also support`Vue 2.0`and`Vue 3.0`.
4
4
5
5
Browser compatibility`TinyVue`The latest versions of mainstream browsers are supported: Chrome, Edge, Firefox, Opera, and Safari. No longer supported`Internet Explorer`.
6
6
7
-
###Installing Node.js
7
+
## Installing Node.js
8
8
9
9
Recommended Installation`v16.13.0`version, if the local`Node.js`, run the following command to check whether the version is correct:
10
10
11
11
```bash
12
12
node -v
13
13
```
14
14
15
-
###Installing Yarn
15
+
## Installing Yarn
16
16
17
17
management`npm`There are two main tools for the package. One is the installation.`Node.js`When it comes`npm`, the other is the faster`yarn`, run the following command to install:
Copy file name to clipboardExpand all lines: examples/sites/demos/pc/webdoc/faq-en.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
##FAQ
1
+
# FAQ
2
2
3
-
###1、Popup element misaligned and flipped in wujie micro front-end
3
+
## 1、Popup element misaligned and flipped in wujie micro front-end
4
4
5
5
_Reason:_ The popup element has a boundary detection logic, and in sub applications, the width and height of 'window' may be much smaller than that of the viewport,
6
6
therefore, it can misjudge boundaries, leading to issues such as flipping and misalignment.
Copy file name to clipboardExpand all lines: examples/sites/demos/pc/webdoc/form-valid-en.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
-
##Form Verification Configuration
1
+
# Form Verification Configuration
2
2
3
3
<br>
4
4
<br>
5
5
6
6
Form validation is based on`async-validator`Encapsulated, mainly used`validate`Function and`rules`Configuration rules of the.
7
7
8
-
###API
8
+
## API
9
9
10
-
####validate
10
+
### validate
11
11
12
12
When submitting a form, the system verifies the fields to be verified in the entire form to obtain the verification result. The following is an example:
13
13
@@ -21,11 +21,11 @@ Parameter description:
21
21
22
22
-`error`: Array type, including fields that do not pass the verification.
23
23
24
-
###Rules
24
+
## Rules
25
25
26
26
Used to set the verification rules for each field to be verified in the form, including the verification type of each field, whether it is mandatory, and the prompt information indicating that the verification fails.
27
27
28
-
####type
28
+
### type
29
29
30
30
through`type`Set the verification type of the field to be verified. With this function, we can verify some specific fields without writing regular rules and making judgments. The following is an example:
31
31
@@ -67,15 +67,15 @@ The values that can be set are as follows:
67
67
68
68
-`any`: any type
69
69
70
-
####required
70
+
### required
71
71
72
72
`required`The attribute value of is of the Boolean type, which is used to set whether a field is mandatory, that is, non-empty verification.
73
73
74
74
-`true`: Set to`true`, indicates that the field is mandatory and the label is marked with a red asterisk \*.
75
75
76
76
-`false`: default value, indicating that the field is not mandatory. The label does not contain red asterisks \*.
77
77
78
-
####pattern
78
+
### pattern
79
79
80
80
Configure the regular expression used to verify the field. The following is an example:
81
81
@@ -85,7 +85,7 @@ rules: {
85
85
}
86
86
```
87
87
88
-
####min
88
+
### min
89
89
90
90
For the string and array types, the lengths are compared. For the number type, the number cannot be less than`min`. An example is as follows:
91
91
@@ -95,7 +95,7 @@ rules: {
95
95
}
96
96
```
97
97
98
-
####max
98
+
### max
99
99
100
100
For the string and array types, the lengths are compared. For the number type, the number cannot be greater than`max`. An example of the use is as follows:
101
101
@@ -105,7 +105,7 @@ rules: {
105
105
}
106
106
```
107
107
108
-
####len
108
+
### len
109
109
110
110
To verify the exact length of the field, specify`len`Property. For string and array types, the length property is compared. For type number, this property indicates an exact match for that number, that is, it can only be strictly equal to`len`. If`len`Attribute vs.`min`and`max`Attributes are used together, then`len`Preferred. Examples of usage are as follows:
111
111
@@ -115,7 +115,7 @@ rules: {
115
115
}
116
116
```
117
117
118
-
####trigger
118
+
### trigger
119
119
120
120
Configure the way to trigger the verification rules through `trigger`. When it is `change`, the verification is triggered when the input box value changes. When it is `blur`,
121
121
the verification is triggered after the input box value is out of focus. Can be set to an array `['change', 'blur']` to trigger both scenarios. The default is to trigger both scenarios.
@@ -137,7 +137,7 @@ The configurable values are as follows:
137
137
138
138
- `change`: The verification is triggered when the value in the input box changes.
139
139
140
-
#### enum
140
+
### enum
141
141
142
142
Enumerated value validation, which verifies whether the value of the field is in`enum`Attribute configuration array`['admin', 'user', 'guest']`Medium. For example:
143
143
@@ -147,7 +147,7 @@ rules: {
147
147
}
148
148
````
149
149
150
-
####whitespace
150
+
### whitespace
151
151
152
152
Verify that mandatory fields have only spaces. Mandatory fields that contain only blanks are generally considered an error. To treat a string consisting only of spaces as an error, you can set`whitespace`for`true`If this parameter is not configured, the input value of all spaces is valid.
153
153
@@ -157,7 +157,7 @@ rules: {
157
157
}
158
158
```
159
159
160
-
####fields
160
+
### fields
161
161
162
162
deep rule. If you need to validate deep object properties, you can assign nested rules to the rule's`fields`Attribute to validate an object or array validation rule. Note that if you do not specify on the parent rule`required`Property, the field is not declared to be fully valid on the source object, and the deep validation rule will not be enforced because there are no verifiable objects. For example:
163
163
@@ -192,7 +192,7 @@ rules: {
192
192
}
193
193
```
194
194
195
-
####defaultField
195
+
### defaultField
196
196
197
197
`defaultField`Attributes can be used with array or object types to validate all values of the container. It can be an object or an array containing validation rules. For example:
198
198
@@ -205,7 +205,7 @@ rules: {
205
205
}
206
206
```
207
207
208
-
####transform
208
+
### transform
209
209
210
210
Sometimes it is necessary to convert values before validation to force or in some way clean them up.`transform`, add a feature to the validation rule. Before validation, the attribute is converted and then reassigned to the source object to change the value of the attribute. For example, the space entered by the user is removed.
211
211
@@ -222,7 +222,7 @@ rules: {
222
222
}
223
223
```
224
224
225
-
####messages
225
+
### messages
226
226
227
227
This parameter is used to configure the message displayed when field verification fails. Internationalization is supported.
228
228
@@ -250,7 +250,7 @@ rules: {
250
250
}
251
251
```
252
252
253
-
####validator
253
+
### validator
254
254
255
255
By`validator`The options are customized for a field.`callback`Must be invoked.
256
256
@@ -278,7 +278,7 @@ rules: {
278
278
}
279
279
```
280
280
281
-
####asyncValidator
281
+
### asyncValidator
282
282
283
283
By`asyncValidator`The option is to perform custom asynchronous validation for a field.`callback`Must be invoked.
0 commit comments