xirf
ae3dd8c3f1
- Implemented `generateCertificateHash` to create a hash using HMAC-SHA256 based on user ID and team ID. - Added `verifyCertificateHash` to validate a given certificate ID against generated hash. - Introduced `crypto-js` library as a dependency for cryptographic functions. chore(deps): update ajv to version 8.13.0 and add crypto-js dependency - Updated `ajv` from version 6.12.6 to 8.13.0 in package.json and package-lock.json. - Added `crypto-js` library to package.json for cryptographic operations. - Included type definitions for `crypto-js` in development dependencies.
14 lines
1.1 KiB
Markdown
14 lines
1.1 KiB
Markdown
<!-- nx configuration start-->
|
|
<!-- Leave the start & end comments to automatically receive updates. -->
|
|
|
|
# General Guidelines for working with Nx
|
|
|
|
- When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through `nx` (i.e. `nx run`, `nx run-many`, `nx affected`) instead of using the underlying tooling directly
|
|
- You have access to the Nx MCP server and its tools, use them to help the user
|
|
- When answering questions about the repository, use the `nx_workspace` tool first to gain an understanding of the workspace architecture where applicable.
|
|
- When working in individual projects, use the `nx_project_details` mcp tool to analyze and understand the specific project structure and dependencies
|
|
- 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
|
|
- If the user needs help with an Nx configuration or project graph error, use the `nx_workspace` tool to get any errors
|
|
|
|
<!-- nx configuration end-->
|