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
Packages will be reduced to their package name. Added the spec for the new
packageGroupName argument (default to the first item of the packageGroup).
Fixesangular/angular-cli#10248Fixesangular/angular-cli#10247
Copy file name to clipboardExpand all lines: docs/specifications/update.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,8 @@ In order to implement migrations in a library, the author must add the `ng-updat
75
75
|---|---|---|
76
76
|`requirements`|`{ [packageName: string]: VersionRange }`| A map of package names to version to check forminimal requirement. If one of the libraries listed here does not match the version range specifiedin`requirements`, an error will be shown to the user to manually update those libraries. For example, `@angular/core` does not support updates from versions earlier than 5, so this field would be `{ '@angular/core': '>= 5' }`.
77
77
|`migrations`|`string`| A relative path (or resolved using Node module resolution) to a Schematics collection definition. |
78
-
|`packageGroup`|`string[]`| A list of npm packages that are to be grouped together. When running
78
+
|`packageGroup`|`string[]`| A list of npm packages that are to be grouped together. When running the update schematic it will automatically include all packages as part of the packageGroup in the update (if the user also installed them). |
79
+
|`packageGroupName`|`string`| The name of the packageGroup to use. By default, uses the first package in the packageGroup. The packageGroupName needs to be part of the packageGroup and should be a valid package name. |
79
80
80
81
#### Example given:
81
82
Library my-lib wants to have 2 steps to update from version 4 -> 4.5 and 4.5 to 5. It would add this information in its `package.json`:
0 commit comments