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: docs/documentation/docs/guides/migrate-from-v1.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
# Migrating from v1 to v2
2
-
Most of the controls have no breaking changes when moving from v1 to v2. However, some APIs were changed to make the libary more stable and controls behavior more even.
2
+
Most of the controls have no breaking changes when moving from v1 to v2. However, some APIs were changed to make the library more stable and controls behavior more even.
3
3
Also, we've bumped up React and Fluent UI versions used in the library. It means you will need to update `package.json` file in your SPFx projects.
4
4
The below guide is an overview of what it takes to migrate from v1 to v2. If we missed something, please let us know in the issues list so we can update the guide. Thanks!
5
5
6
6
## v2 Supports SharePoint Online Only
7
-
v2 of Reusable Controls is based on SharePoint Framework 1.11 and, as a result, does not support SharePoint On-Premise. **Please, use v1 if you plan to deploy your soluition on-prem.**
7
+
v2 of Reusable Controls is based on SharePoint Framework 1.11 and, as a result, does not support SharePoint On-Premise. **Please, use v1 if you plan to deploy your solution on-prem.**
8
8
9
9
## React and Fluent UI versions
10
10
v2 of Reusable Controls uses React.js v16.8.5 and Fluent UI (Office UI Fabric React) v6.189.2.
@@ -28,9 +28,9 @@ Please, update the `package.json` accordingly:
28
28
`isRequred` is renamed to `required`.<br/>
29
29
The property has been renamed to use the common approach for mandatory field naming.
30
30
31
-
`errorMessage` represents static error message to be displayed in the control. <br />
31
+
`errorMessage` represents a static error message to be displayed in the control. <br />
32
32
In v1 `errorMessage` is used to provide the text that will be displayed if the field is set as `required` and no value is selected.
33
-
In v2 you can use this property to statically display error message for whatever reason.
33
+
In v2 you can use this property to display an error message for whatever reason statically.
34
34
```typescript
35
35
/**
36
36
* Static error message displayed below the text field. Use onGetErrorMessage to dynamically change the error message displayed (if any) based on the current value. errorMessage and onGetErrorMessage are mutually exclusive (errorMessage takes precedence).
@@ -42,7 +42,7 @@ In v2 you can use this property to statically display error message for whatever
42
42
The method is used to get the validation error message and determine whether the input value is valid or not. Mutually exclusive with the static string errorMessage (it will take precedence over this).
43
43
```typescript
44
44
/**
45
-
* The method is used to get the validation error message and determine whether the picker value is valid or not.
45
+
* The method is used to get the validation error message and determine whether the picker value is valid.
46
46
* Mutually exclusive with the static string errorMessage (it will take precedence over this).
0 commit comments