Skip to content

Commit 132541e

Browse files
Merge pull request #1564 from IgniteUI/mstoyanova/upgrade_packages
feat: add upgrade instructions for licensed packages in Angular, Reac…
2 parents 4c0fb6a + 2e95b71 commit 132541e

3 files changed

Lines changed: 49 additions & 3 deletions

File tree

packages/igniteui-mcp/igniteui-doc-mcp/src/tools/setup_angular.md

Lines changed: 23 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,4 +78,26 @@ Once the project is running:
7878
1. Call `list_components` or `search_docs` to find the component you want to add.
7979
2. Call `get_doc` with the component name to get full usage instructions.
8080
3. Call `get_api_reference` or `search_api` to look up properties, methods, and events.
81-
4. Apply theming via the **igniteui-theming MCP** before or after adding components.
81+
4. Apply theming via the **igniteui-theming MCP** before or after adding components.
82+
83+
**Use the next paragraph only if the user explicitly asks to upgrade to licensed packages or switch from trial to licensed.**
84+
85+
## Upgrade to Licensed Packages
86+
87+
If the project contains `ignite-ui-cli.json` then upgrade using the **Ignite UI Angular Schematics** or the **Ignite UI CLI**, depending on which is already installed in the dependencies. If not, then refer to docs about licensing.
88+
89+
**Angular Schematics:**
90+
91+
```bash
92+
ng g @igniteui/angular-schematics:upgrade-packages
93+
```
94+
95+
**Ignite UI CLI:**
96+
97+
```bash
98+
ig upgrade-packages
99+
```
100+
101+
The command updates package dependencies and source references. You will be prompted to log in to the Infragistics npm registry if not already configured.
102+
103+
---

packages/igniteui-mcp/igniteui-doc-mcp/src/tools/setup_react.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,4 +63,16 @@ Once the project is running:
6363
1. Call `list_components` or `search_docs` to find the component you want to add.
6464
2. Call `get_doc` with the component name to get full usage instructions.
6565
3. Call `get_api_reference` or `search_api` to look up properties, methods, and events.
66-
4. Apply theming via the **igniteui-theming MCP** before or after adding components.
66+
4. Apply theming via the **igniteui-theming MCP** before or after adding components.
67+
68+
**Use the next paragraph only if the user explicitly asks to upgrade to licensed packages or switch from trial to licensed.**
69+
70+
## Upgrade to Licensed Packages
71+
72+
If the project contains `ignite-ui-cli.json` then upgrade using the **Ignite UI CLI**. If not, then refer to docs about licensing.
73+
74+
```bash
75+
ig upgrade-packages
76+
```
77+
78+
The command updates package dependencies and source references. You will be prompted to log in to the Infragistics npm registry if not already configured.

packages/igniteui-mcp/igniteui-doc-mcp/src/tools/setup_webcomponents.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,4 +59,16 @@ Once the project is running:
5959
1. Call `list_components` or `search_docs` to find the component you want to add.
6060
2. Call `get_doc` with the component name to get full usage instructions.
6161
3. Call `get_api_reference` or `search_api` to look up properties, methods, and events.
62-
4. Apply theming via the **igniteui-theming MCP** before or after adding components.
62+
4. Apply theming via the **igniteui-theming MCP** before or after adding components.
63+
64+
**Use the next paragraph only if the user explicitly asks to upgrade to licensed packages or switch from trial to licensed.**
65+
66+
## Upgrade to Licensed Packages
67+
68+
If the project contains `ignite-ui-cli.json` then upgrade using the **Ignite UI CLI**. If not, then refer to docs about licensing.
69+
70+
```bash
71+
ig upgrade-packages
72+
```
73+
74+
The command updates package dependencies and source references. You will be prompted to log in to the Infragistics npm registry if not already configured.

0 commit comments

Comments
 (0)