Skip to content

Commit e91b1b3

Browse files
renovate[bot]ryanbas21
authored andcommitted
chore(deps): update dependency @reduxjs/toolkit to v2.8.2
1 parent b0f467d commit e91b1b3

3 files changed

Lines changed: 73 additions & 14 deletions

File tree

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
applyTo: '**'
3+
---
4+
5+
// This file is automatically generated by Nx Console
6+
7+
You are in an nx workspace using Nx 20.5.0 and pnpm as the package manager.
8+
9+
You have access to the Nx MCP server and the tools it provides. Use them. Follow these guidelines in order to best help the user:
10+
11+
# General Guidelines
12+
- When answering questions, use the nx_workspace tool first to gain an understanding of the workspace architecture
13+
- For questions around nx configuration, best practices or if you're unsure, use the nx_docs tool to get relevant, up-to-date docs!! Always use this instead of assuming things about nx configuration
14+
- If the user needs help with an Nx configuration or project graph error, use the 'nx_workspace' tool to get any errors
15+
- To help answer questions about the workspace structure or simply help with demonstrating how tasks depend on each other, use the 'nx_visualize_graph' tool
16+
17+
# Generation Guidelines
18+
If the user wants to generate something, use the following flow:
19+
20+
- learn about the nx workspace and any specifics the user needs by using the 'nx_workspace' tool and the 'nx_project_details' tool if applicable
21+
- get the available generators using the 'nx_generators' tool
22+
- decide which generator to use. If no generators seem relevant, check the 'nx_available_plugins' tool to see if the user could install a plugin to help them
23+
- get generator details using the 'nx_generator_schema' tool
24+
- you may use the 'nx_docs' tool to learn more about a specific generator or technology if you're unsure
25+
- decide which options to provide in order to best complete the user's request. Don't make any assumptions and keep the options minimalistic
26+
- open the generator UI using the 'nx_open_generate_ui' tool
27+
- wait for the user to finish the generator
28+
- read the generator log file using the 'nx_read_generator_log' tool
29+
- use the information provided in the log file to answer the user's question or continue with what they were doing
30+
undefined
31+
32+
# CI Error Guidelines
33+
If the user wants help with fixing an error in their CI pipeline, use the following flow:
34+
- Retrieve the list of current CI Pipeline Executions (CIPEs) using the 'nx_cloud_cipe_details' tool
35+
- If there are any errors, use the 'nx_cloud_fix_cipe_failure' tool to retrieve the logs for a specific task
36+
- Use the task logs to see what's wrong and help the user fix their problem. Use the appropriate tools if necessary
37+
- Make sure that the problem is fixed by running the task that you passed into the 'nx_cloud_fix_cipe_failure' tool
38+
39+

pnpm-lock.yaml

Lines changed: 33 additions & 13 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

pnpm-workspace.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,5 +7,5 @@ packages:
77
- tools/**
88

99
catalog:
10-
'@reduxjs/toolkit': ^2.2.5
10+
'@reduxjs/toolkit': ^2.8.2
1111
immer: ^10.1.1

0 commit comments

Comments
 (0)