Linking service #5
Conversation
WalkthroughThe recent changes enhance the identity-authentication-platform project, focusing on improved logging, error handling, and modularity through the integration of new services and configuration management. The addition of the Lit Protocol libraries expands the platform's capabilities, while modifications to existing services streamline workflows and enhance type safety. The pre-commit and pre-push hooks have been refined to emphasize better code quality checks before deployments. Changes
Sequence Diagram(s)sequenceDiagram
participant C as Client
participant P as Pre-push Hook
participant T as Test Suite
participant L as Linting Tool
C->>P: Initiate Push
P->>T: Run npm test
T-->>P: Test Results
P->>L: Run npx lint-staged
L-->>P: Lint Results
P-->>C: Push Success
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Outside diff range, codebase verification and nitpick comments (1)
src/shared/decorators/jwt-provider.decorator.ts (1)
1-5: Ensure consistent import style.The imports from
class-validatorcan be grouped into a single line for better readability.- import { - registerDecorator, - ValidationOptions, - ValidationArguments, - } from 'class-validator' + import { registerDecorator, ValidationOptions, ValidationArguments } from 'class-validator'
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
Files selected for processing (29)
- .husky/pre-commit (1 hunks)
- .husky/pre-push (1 hunks)
- package.json (1 hunks)
- src/app.module.ts (2 hunks)
- src/auth-siwe/dto/verify-siwe.dto.ts (1 hunks)
- src/auth-siwe/siwe.service.spec.ts (2 hunks)
- src/auth-siwe/siwe.service.ts (1 hunks)
- src/auth/auth.service.ts (1 hunks)
- src/auth/oAuth.service.spec.ts (2 hunks)
- src/auth/oAuth.service.ts (5 hunks)
- src/config/index.ts (2 hunks)
- src/config/pino.config.ts (1 hunks)
- src/eas/eas.service.ts (8 hunks)
- src/linking/dto/link-identities.dto.ts (1 hunks)
- src/linking/linking.controller.ts (2 hunks)
- src/linking/linking.module.ts (1 hunks)
- src/lit/config/lit.config.ts (1 hunks)
- src/lit/constants/network.constants.ts (1 hunks)
- src/lit/lit.module.ts (1 hunks)
- src/lit/lit.service.ts (1 hunks)
- src/main.ts (1 hunks)
- src/shared/constants/chain.constants.ts (2 hunks)
- src/shared/decorators/jwt-provider.decorator.ts (1 hunks)
- src/shared/types/chain.type.ts (1 hunks)
- src/utils/data-utils.service.spec.ts (1 hunks)
- src/utils/data-utils.service.ts (1 hunks)
- src/utils/utils.module.ts (1 hunks)
- src/utils/viem.service.spec.ts (1 hunks)
- src/utils/viem.utils.service.ts (2 hunks)
Files skipped from review due to trivial changes (4)
- .husky/pre-commit
- src/auth-siwe/dto/verify-siwe.dto.ts
- src/lit/constants/network.constants.ts
- src/utils/viem.service.spec.ts
Additional comments not posted (74)
.husky/pre-push (1)
1-2: LGTM! Pre-push hooks for tests and linting are beneficial.The pre-push hooks ensure that tests are run and code is linted before pushing changes, which helps maintain code quality.
src/lit/lit.module.ts (1)
1-9: LGTM! The module structure is clean and follows NestJS conventions.The LitModule is well-defined, registering the LitService as a provider and exporter. This promotes modularity and reusability.
src/shared/types/chain.type.ts (1)
1-5: LGTM! The type definitions are clear and promote type safety.The types for supported chain IDs and Lit chains are well-defined using existing constants and types from the Lit Protocol, ensuring consistency.
src/lit/config/lit.config.ts (3)
1-2: LGTM! Imports are appropriate.The imports for
JoiandregisterAsare correctly used for configuration and validation purposes.
4-6: LGTM! Configuration registration is correct.The configuration is registered under the name 'lit' and reads the
LIT_NETWORKenvironment variable.
8-10: LGTM! Configuration schema is correctly implemented.The schema uses
Joito validate thatLIT_NETWORKis a required string.src/linking/linking.module.ts (2)
3-3: LGTM! Imports are appropriate.The import path for
EasModulehas been corrected to lowercase, andLitModulehas been added for additional functionality.Also applies to: 6-6
9-9: LGTM! Module imports array is correctly updated.The
importsarray in the@Moduledecorator has been updated to includeLitModule, expanding the module's dependencies.src/utils/utils.module.ts (2)
5-5: LGTM! Import statement is appropriate.The import statement correctly includes
DataUtilsService.
8-19: LGTM! Providers and exports arrays are correctly updated.The
providersandexportsarrays in the@Moduledecorator have been updated to includeDataUtilsService, enhancing the module's functionality.src/config/pino.config.ts (2)
4-5: Approved: Enhanced configurability for log level.The log level is now retrieved from the
ConfigService, allowing for more flexible log level management.
8-8: Approved: Consistent log level usage.The log level is now set using the dynamically retrieved value, ensuring consistency in the logging configuration.
src/utils/data-utils.service.ts (2)
1-2: Approved: Necessary import for NestJS service.The import of
Injectablefrom@nestjs/commonis necessary for defining the service as injectable in NestJS.
3-4: Approved: Service class definition.The
DataUtilsServiceclass is defined and marked as injectable, which is necessary for creating a service in NestJS.src/config/index.ts (3)
12-12: Approved: Import forlitmodule configuration.The import of
litConfigandlitConfigSchemafrom thelitmodule is necessary for integrating thelitmodule into the configuration management.
20-20: Approved: Addition oflitConfigto configuration modules.The
litConfigis added to theconfigModulesarray, which is necessary for including thelitmodule in the configuration setup.
32-32: Approved: Addition oflitConfigSchemato configuration validation schema.The
litConfigSchemais added to theconfigValidationSchemaobject, which is necessary for validating the configuration of thelitmodule.src/linking/dto/link-identities.dto.ts (3)
3-4: LGTM! New imports for JWT handling.The new imports for
JwtProviderandAUTH_PROVIDERSare correct and necessary for the new functionality.
8-16: LGTM! Enhanced clarity and specificity in JWT handling.The
walletJwtproperty has been renamed tosiweJwtand its description updated. The new@JwtProviderdecorator ties the JWT to a specific provider, enhancing functionality.
19-19: LGTM! Updated description foranyJwt.The description for
anyJwthas been updated to reflect the change from 'wallet JWT' to 'siwe JWT', maintaining consistency and clarity.src/app.module.ts (2)
11-11: LGTM! New import forLitModule.The import statement for
LitModuleis correct and necessary for the new functionality.
30-30: LGTM! Inclusion ofLitModuleinimportsarray.The inclusion of
LitModulein theimportsarray expands the application's functionality and is correctly placed.src/utils/viem.utils.service.ts (3)
2-3: LGTM! Updated imports for type safety.The import statements for
SUPPORTED_CHAIN_IDSandSupportedChainIdare correct and necessary for the new functionality.
28-28: LGTM! Enhanced type safety forgetPublicClient.The parameter type for
getPublicClienthas been changed fromnumbertoSupportedChainId, enhancing type safety.
32-32: LGTM! Enhanced type safety foridToChain.The parameter type for
idToChainhas been changed fromnumbertoSupportedChainId, enhancing type safety.src/shared/decorators/jwt-provider.decorator.ts (1)
8-36: LGTM! Ensure proper error handling and validation.The
JwtProviderdecorator is well-implemented. It correctly validates the JWT token based on the expected provider and provides a clear error message when validation fails.However, ensure that the
valuepassed to thevalidatemethod is always a valid JWT token to avoid potential runtime errors.Verification successful
Verification Successful: Proper error handling and validation are ensured.
The
JwtProviderdecorator'svalidatemethod relies on theauthService.validateTokenmethod, which correctly validates JWT tokens and throws errors for invalid tokens. This ensures that thevaluepassed to thevalidatemethod is always a valid JWT token.
authService.validateTokenmethod implementation and test cases confirm proper validation.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that the `JwtProvider` decorator is used correctly and that the `value` passed to the `validate` method is always a valid JWT token. # Test: Search for the usage of the `JwtProvider` decorator. Expect: Proper usage with valid JWT tokens. rg --type ts -A 5 $'@JwtProvider'Length of output: 431
Script:
#!/bin/bash # Description: Verify that the `siweJwt` property is always assigned a valid JWT token. # Search for the definition and assignment of the `siweJwt` property within the `src/linking/dto/link-identities.dto.ts` file. rg --type ts 'siweJwt' -A 10 -B 10Length of output: 3978
Script:
#!/bin/bash # Description: Verify the implementation of the `validateToken` method in the `authService`. # Search for the implementation of the `validateToken` method in the TypeScript files. rg --type ts 'validateToken' -A 10 -B 10Length of output: 5035
src/auth-siwe/siwe.service.ts (2)
10-14: LGTM! Enhanced logging withPinoLogger.The addition of
PinoLoggerimproves the logging capabilities of theSiweServiceclass.
21-36: LGTM! Improved error handling inverifySiweMessage.The restructuring of the
verifySiweMessagemethod enhances error handling and logging, making it easier to diagnose issues during execution.src/main.ts (1)
14-16: Approved: Reordered middleware setup enhances logging and error handling.Reordering the middleware setup ensures that logging and error handling mechanisms are established before validation pipes. This can improve the application's ability to log errors and handle exceptions effectively during the request lifecycle.
src/utils/data-utils.service.spec.ts (4)
15-17: Approved: Basic service definition test.This test case ensures that the
DataUtilsServiceis properly instantiated and defined.
19-39: Approved: BigInt value conversion test.This test case verifies that the
formatBigIntValuesmethod correctly converts BigInt values to strings or numbers, ensuring the core functionality is working as expected.
41-44: Approved: Null and undefined value handling test.This test case ensures that the
formatBigIntValuesmethod can gracefully handle edge cases involving null and undefined inputs.
46-53: Approved: Non-BigInt value handling test.This test case ensures that the
formatBigIntValuesmethod leaves non-BigInt values unchanged, maintaining data integrity.src/linking/linking.controller.ts (2)
15-17: Approved: Constructor dependency changes.The constructor now includes
LitServiceandDataUtilsServiceinstead ofViemUtilsService, reflecting a shift in dependencies to support new functionalities related to data encryption and utility operations.
28-52: Approved: Enhanced security and data handling inlinkIdentitiesmethod.The
linkIdentitiesmethod now includes additional parameters in the input DTO, retrieves and validates payloads for bothanyJwtandsiweJwt, useslitServicefor encryption, and formats the response usingdataUtilsService. These changes enhance security and data handling.src/auth-siwe/siwe.service.spec.ts (4)
4-4: LGTM! ImportingPinoLoggerandLoggerModuleThe addition of
PinoLoggerandLoggerModulealigns with the goal of improving logging capabilities.
10-10: LGTM! DeclaringloggerMockThe declaration of
loggerMockis appropriate for mocking the logger in tests.
17-17: LGTM! InitializingloggerMockThe initialization of
loggerMockwith a mockederrormethod is appropriate for testing error logging.
Line range hint
20-34:
LGTM! Enhancing TestingModule configurationThe
TestingModuleconfiguration changes, including importingLoggerModule.forRoot()and providingPinoLoggerusingloggerMock, enhance the test module by integrating structured logging.package.json (1)
28-32: LGTM! Adding Lit Protocol dependenciesThe addition of
@lit-protocol/auth-helpers,@lit-protocol/constants,@lit-protocol/contracts-sdk,@lit-protocol/lit-node-client-nodejs, and@lit-protocol/typesenhances the platform's capabilities, potentially integrating new authentication or blockchain functionalities.src/lit/lit.service.ts (11)
1-16: LGTM! Importing necessary modulesThe import statements include necessary modules from
@nestjs/common,@lit-protocol/lit-node-client-nodejs,@lit-protocol/types, and other related dependencies, which are essential for the functionality provided by theLitServiceclass.
18-22: LGTM! DefiningLitServiceclass and constructorThe
LitServiceclass definition and constructor setup, including the logger andLitNodeClientNodeJsinstance, are appropriate for initializing the service with necessary dependencies.
24-30: LGTM! ImplementingconnectmethodThe
connectmethod initializes theLitNodeClientNodeJswith network configuration and connects it, which is essential for establishing a connection to the Lit network.
32-35: LGTM! ImplementingdisconnectmethodThe
disconnectmethod disconnects theLitNodeClientNodeJsand sets it to null, which is necessary for properly closing the connection to the Lit network.
37-45: LGTM! ImplementinggetNetworkConfigmethodThe
getNetworkConfigmethod retrieves the network configuration based on the provided network name, which is essential for obtaining the correct network configuration for the Lit network.
47-55: LGTM! ImplementinggetContractAddressmethodThe
getContractAddressmethod retrieves the contract address based on the provided chain ID, which is necessary for obtaining the correct contract address for the specified chain.
57-65: LGTM! ImplementinggetContractFunctionNamemethodThe
getContractFunctionNamemethod retrieves the contract function name based on the provided chain ID, which is essential for obtaining the correct contract function name for the specified chain.
67-75: LGTM! ImplementinggetContractAbimethodThe
getContractAbimethod retrieves the contract ABI based on the provided chain ID, which is necessary for obtaining the correct contract ABI for the specified chain.
77-83: LGTM! ImplementingchainIdToLitChainNamemethodThe
chainIdToLitChainNamemethod maps a chain ID to a Lit chain name, which is essential for mapping chain IDs to Lit chain names.
84-101: LGTM! ImplementinggenerateEvmContractConditionsmethodThe
generateEvmContractConditionsmethod generates EVM contract conditions based on the provided chain ID and address, which is necessary for generating the correct EVM contract conditions for the specified chain and address.
104-126: LGTM! ImplementingencryptmethodThe
encryptmethod encrypts data using the Lit Protocol based on the provided chain ID and user address, which is essential for encrypting data using the Lit Protocol.src/auth/oAuth.service.ts (4)
22-24: LGTM! Improved logging with PinoLogger.The change to use
PinoLoggerinstead ofLoggerenhances structured logging.
86-92: LGTM! Enhanced error logging.The error logging now captures detailed information, improving debugging capabilities.
115-121: LGTM! Enhanced error logging.The error logging now captures detailed information, improving debugging capabilities.
135-147: LGTM! Simplified control flow and improved error handling.The validation of the state is now the first operation performed, ensuring any invalid state is handled upfront, which clarifies the control flow and improves error handling.
src/auth/oAuth.service.spec.ts (3)
14-14: LGTM! Added loggerMock for testing.The loggerMock facilitates logging during tests, improving debugging capabilities.
58-58: LGTM! Imported LoggerModule for testing.The LoggerModule provides logging capabilities within the testing environment, enhancing the ability to track and log events during tests.
65-65: LGTM! Provided PinoLogger for testing.The PinoLogger is injected into services that require logging during tests, improving the ability to track and log events.
src/eas/eas.service.ts (10)
26-27: LGTM! Imported SupportedChainId for type safety.The import of
SupportedChainIdenhances type safety by ensuring only supported chain IDs are used.
58-58: LGTM! Updated getContract method signature.The update ensures that only supported chain IDs are passed to the method, enhancing type safety.
62-69: LGTM! Updated getSchemaUUID method signature.The update ensures that only supported chain IDs are passed to the method, enhancing type safety.
Line range hint
71-78:
LGTM! Updated getContractAddress method signature.The update ensures that only supported chain IDs are passed to the method, enhancing type safety.
80-87: LGTM! Updated getContractABI method signature.The update ensures that only supported chain IDs are passed to the method, enhancing type safety.
Line range hint
90-97:
LGTM! Updated getDomain method signature.The update ensures that only supported chain IDs are passed to the method, enhancing type safety.
103-106: LGTM! Updated getNounce method signature.The update ensures that only supported chain IDs are passed to the method, enhancing type safety.
Line range hint
128-132:
LGTM! Updated createDelegatedAttestationRequest method signature.The update ensures that only supported chain IDs are passed to the method, enhancing type safety.
143-146: LGTM! Updated createAttestationMessage method signature.The update ensures that only supported chain IDs are passed to the method, enhancing type safety.
Line range hint
183-188:
LGTM! Updated getDelegatedAttestationRequest method signature.The update ensures that only supported chain IDs are passed to the method, enhancing type safety.
src/shared/constants/chain.constants.ts (6)
848-849: Verify the usage ofpermissionManagerContractAddressin the codebase.A new property
permissionManagerContractAddresshas been introduced. Ensure that it is used correctly in the codebase.Verification successful
The usage of
permissionManagerContractAddressis verified in the codebase.The property
permissionManagerContractAddressis correctly used insrc/lit/lit.service.tsto return the contract address.
src/lit/lit.service.ts:return chain.permissionManagerContractAddress as '0x${string}'Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the usage of `permissionManagerContractAddress` in the codebase. # Test: Search for the new property name. Expect: Occurrences of `permissionManagerContractAddress` in relevant files. rg --type typescript -A 5 $'permissionManagerContractAddress'Length of output: 95
Script:
#!/bin/bash # Description: Verify the usage of `permissionManagerContractAddress` in the codebase. # Test: Search for the new property name. Expect: Occurrences of `permissionManagerContractAddress` in relevant files. rg --type-add 'ts:*.ts' -t ts -A 5 'permissionManagerContractAddress'Length of output: 906
4-4: Verify the usage ofeasSchemaUUIDin the codebase.The property
schemaUUIDhas been renamed toeasSchemaUUID. Ensure that all references toschemaUUIDare updated accordingly.Verification successful
Verification successful
All references to
schemaUUIDhave been updated toeasSchemaUUIDacross the codebase.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify all references to `schemaUUID` are updated to `easSchemaUUID`. # Test: Search for the old property name. Expect: No occurrences of `schemaUUID`. rg --type typescript -A 5 $'schemaUUID'Length of output: 73
Script:
#!/bin/bash # Description: Verify all references to `schemaUUID` are updated to `easSchemaUUID`. # Test: Search for the old property name. Expect: No occurrences of `schemaUUID`. rg --glob '*.ts' -A 5 'schemaUUID'Length of output: 34
9-9: Verify the usage ofeasContractAbiin the codebase.The property
abihas been renamed toeasContractAbi. Ensure that all references toabiare updated accordingly.Verification successful
Verify the usage of
easContractAbiin the codebase.The property
abihas been successfully renamed toeasContractAbiin the relevant files.
src/shared/constants/chain.constants.tssrc/eas/eas.service.tsScripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify all references to `abi` are updated to `easContractAbi`. # Test: Search for the old property name. Expect: No occurrences of `abi`. rg --type typescript -A 5 $'abi'Length of output: 66
Script:
#!/bin/bash # Description: Verify all references to `abi` are updated to `easContractAbi`. # Test: Search for the old property name. Expect: No occurrences of `abi`. rg --glob '*.ts' -A 5 $'abi'Length of output: 19023
Script:
#!/bin/bash # Description: Verify all references to `abi` are updated to `easContractAbi`. # Test: Search for the new property name. Expect: Occurrences of `easContractAbi`. rg --glob '*.ts' -A 5 $'easContractAbi'Length of output: 1118
852-865: Verify the usage ofpermissionManagerContractAbiin the codebase.A new property
permissionManagerContractAbihas been introduced. Ensure that it is used correctly in the codebase.Verification successful
Verified the usage of
permissionManagerContractAbi.The new property
permissionManagerContractAbiis correctly used in thegetContractAbimethod withinsrc/lit/lit.service.tsto fetch ABI details for a given chain ID.
src/lit/lit.service.ts:getContractAbimethodScripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the usage of `permissionManagerContractAbi` in the codebase. # Test: Search for the new property name. Expect: Occurrences of `permissionManagerContractAbi` in relevant files. rg --type typescript -A 5 $'permissionManagerContractAbi'Length of output: 91
Script:
#!/bin/bash # Description: Verify the usage of `permissionManagerContractAbi` in the codebase. # Test: Search for the new property name. Expect: Occurrences of `permissionManagerContractAbi` in relevant files. rg --type ts -A 5 'permissionManagerContractAbi'Length of output: 907
Script:
#!/bin/bash # Description: Extract more context around the usage of `permissionManagerContractAbi` in `lit.service.ts`. # Test: Show lines around the usage of `permissionManagerContractAbi` in `lit.service.ts` to understand its context. rg 'permissionManagerContractAbi' -A 10 -B 10 src/lit/lit.service.tsLength of output: 728
869-871: Verify the usage ofSUPPORTED_CHAIN_IDSin the codebase.A new constant
SUPPORTED_CHAIN_IDShas been added. Ensure that it is used correctly in the codebase.Verification successful
Verify the usage of
SUPPORTED_CHAIN_IDSin the codebase.A new constant
SUPPORTED_CHAIN_IDShas been added. Ensure that it is used correctly in the codebase.
Verify the context of
SUPPORTED_CHAIN_IDSusage in the codebase.The new constant
SUPPORTED_CHAIN_IDSis found in multiple files. Ensure that its usage is correct and consistent.
The new constant
SUPPORTED_CHAIN_IDSis used correctly and consistently across the codebase.
src/shared/types/chain.type.ts: Used in type definitions.src/utils/viem.service.spec.ts: Used in test cases.src/utils/viem.utils.service.ts: Used in service methods.src/auth-siwe/dto/verify-siwe.dto.ts: Used in DTO validation.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the usage of `SUPPORTED_CHAIN_IDS` in the codebase. # Test: Search for the new constant name. Expect: Occurrences of `SUPPORTED_CHAIN_IDS` in relevant files. rg --type typescript -A 5 $'SUPPORTED_CHAIN_IDS'Length of output: 82
Script:
#!/bin/bash # Description: Verify the usage of `SUPPORTED_CHAIN_IDS` in the codebase. # Find all TypeScript files and search for the usage of SUPPORTED_CHAIN_IDS fd --extension ts --exec rg 'SUPPORTED_CHAIN_IDS' {}Length of output: 704
Script:
#!/bin/bash # Description: Verify the context of `SUPPORTED_CHAIN_IDS` usage in the codebase. # Search for the context lines around each occurrence of SUPPORTED_CHAIN_IDS rg 'SUPPORTED_CHAIN_IDS' -A 5 -B 5Length of output: 5623
851-851: Verify the usage ofpermissionManagerContractFunctionNamein the codebase.A new property
permissionManagerContractFunctionNamehas been introduced. Ensure that it is used correctly in the codebase.Verification successful
Verified the usage of
permissionManagerContractFunctionNamein the codebase.The property
permissionManagerContractFunctionNameis used correctly within thegetContractFunctionNamemethod insrc/lit/lit.service.ts.
src/lit/lit.service.ts: The method retrieves thechainobject based onchainIdand returns thepermissionManagerContractFunctionNameproperty.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the usage of `permissionManagerContractFunctionName` in the codebase. # Test: Search for the new property name. Expect: Occurrences of `permissionManagerContractFunctionName` in relevant files. rg --type typescript -A 5 $'permissionManagerContractFunctionName'Length of output: 100
Script:
#!/bin/bash # Description: Verify the usage of `permissionManagerContractFunctionName` in the codebase. # Test: Search for the new property name. Expect: Occurrences of `permissionManagerContractFunctionName` in relevant files. rg --glob '*.ts' -A 5 'permissionManagerContractFunctionName'Length of output: 914
Script:
#!/bin/bash # Description: Extract more context around the usage of `permissionManagerContractFunctionName` in `src/lit/lit.service.ts`. # Test: Extract lines around the usage of `permissionManagerContractFunctionName` in `src/lit/lit.service.ts`. rg --glob 'src/lit/lit.service.ts' -A 10 -B 10 'permissionManagerContractFunctionName'Length of output: 1266
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (2)
- src/shared/decorators/jwt-provider.decorator.ts (1 hunks)
- src/utils/data-utils.service.ts (1 hunks)
Files skipped from review as they are similar to previous changes (2)
- src/shared/decorators/jwt-provider.decorator.ts
- src/utils/data-utils.service.ts
Summary by CodeRabbit
New Features
decodeTokenmethod to theAuthServicefor decoding JWT tokens.DataUtilsServicefor formatting BigInt values within data structures.LitServicefor interacting with the Lit Protocol.JwtProviderdecorator for JWT validation.Enhancements
SupportedChainId.litConfigand validation schema.Bug Fixes
Documentation