Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/microsoft dynamics connection #625

Merged
merged 3 commits into from
Aug 7, 2024
Merged

Conversation

naelob
Copy link
Contributor

@naelob naelob commented Aug 7, 2024

Summary by CodeRabbit

  • New Features

    • Updated documentation to now demonstrate product listing instead of file management for the Panora API.
    • Introduced support for Microsoft Dynamics Sales within our CRM integration capabilities.
    • Added dynamic domain format examples in the ProviderModal to improve user experience.
  • Enhancements

    • Enhanced state data structure allowing for more flexible key-value pairs in the ConnectionsController.
    • Improved OAuth2 URL handling specifically for Microsoft Dynamics Sales, adding necessary parameters for better integration.
  • Bug Fixes

    • Corrected naming and scope definitions for the Microsoft Dynamics Sales connector, improving clarity and functionality in the configuration.

@rflihxyz
Copy link
Contributor

rflihxyz commented Aug 7, 2024

Qovery Preview

Qovery can create a Preview Environment for this PR.
To trigger its creation, please post a comment with one of the following command.

Command Blueprint environment
/qovery preview 783d0240-ec38-4387-a9a9-8e225f1bd3e1 dev
/qovery preview {all|UUID1,UUID2,...} To preview multiple environments

This comment has been generated from Qovery AI 🤖.
Below, a word from its wisdom :

There are two hard problems in computer science: naming things, cache invalidation and off-by-1 errors

Copy link

changeset-bot bot commented Aug 7, 2024

⚠️ No Changeset found

Latest commit: b48b551

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Contributor

coderabbitai bot commented Aug 7, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

Walkthrough

The recent updates enhance the integration capabilities of the Panora API, particularly in relation to Ecommerce and Microsoft Dynamics Sales. Key modifications include renaming resources from "files" to "products," enhancing state data handling for greater flexibility, and introducing support for Microsoft Dynamics Sales. These changes aim to improve clarity, functionality, and security for users working with product data and CRM services.

Changes

Files Change Summary
docs/ecommerce/quickstart.mdx Updated terminology from "files" to "products," revising headers, introductory text, and code snippets accordingly to focus on product listing functionality.
packages/api/src/@core/connections/... Enhanced StateDataType to allow dynamic properties and added resource to state handling in ConnectionsController for better service integration.
packages/api/src/@core/connections/crm/... Introduced MicrosoftDynamicsSalesConnectionService to support Microsoft Dynamics Sales, adding it to the module and enhancing CRM capabilities.
packages/api/src/@core/connections/crm/... Implemented OAuth2 logic in the new service for managing connections, handling callbacks, and refreshing tokens with secure token management.
packages/shared/src/authUrl.ts Improved OAuth2 URL handling for Microsoft Dynamics Sales by adding conditional logic for state and constructing URLs with additional parameters.
packages/shared/src/connectors/metadata.ts Renamed Microsoft Dynamics Sales connector key, updated scopes and URLs, introduced new options, and shifted to OAuth2 authentication strategy for security.
apps/magic-link/src/lib/ProviderModal.tsx Added domainFormats constant to assist users with expected domain formats based on selected provider in the ProviderModal component.

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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 9

Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 5611b91 and 55539bd.

Files selected for processing (6)
  • docs/ecommerce/quickstart.mdx (4 hunks)
  • packages/api/src/@core/connections/connections.controller.ts (2 hunks)
  • packages/api/src/@core/connections/crm/crm.connection.module.ts (2 hunks)
  • packages/api/src/@core/connections/crm/services/microsoftdynamicssales/microsoftdynamicssales.service.ts (1 hunks)
  • packages/shared/src/authUrl.ts (2 hunks)
  • packages/shared/src/connectors/metadata.ts (1 hunks)
Additional context used
LanguageTool
docs/ecommerce/quickstart.mdx

[misspelling] ~7-~7: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ..." icon: "star" --- ## List products in a Ecommerce provider using Panora <Check...

(EN_A_VS_AN)

Biome
packages/shared/src/authUrl.ts

[error] 60-60: Forbidden non-null assertion.

Unsafe fix: Replace with optional chain operator ?. This operator includes runtime checks, so it is safer than the compile-only non-null assertion operator

(lint/style/noNonNullAssertion)


[error] 181-181: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 182-182: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)

packages/api/src/@core/connections/crm/services/microsoftdynamicssales/microsoftdynamicssales.service.ts

[error] 25-25: A Node.js builtin module should be imported with the node: protocol.

Using the node: protocol is more explicit and signals that the imported module belongs to Node.js.
Unsafe fix: Add the node: protocol.

(lint/style/useNodejsImportProtocol)


[error] 93-93: The catch clause that only rethrows the original error is redundant.

These unnecessary catch clauses can be confusing. It is recommended to remove them.

(lint/complexity/noUselessCatch)


[error] 134-135: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 189-189: The catch clause that only rethrows the original error is redundant.

These unnecessary catch clauses can be confusing. It is recommended to remove them.

(lint/complexity/noUselessCatch)


[error] 240-240: The catch clause that only rethrows the original error is redundant.

These unnecessary catch clauses can be confusing. It is recommended to remove them.

(lint/complexity/noUselessCatch)

Additional comments not posted (14)
docs/ecommerce/quickstart.mdx (2)

35-41: LGTM!

The changes align with the new functionality of listing products.


Line range hint 53-68:
LGTM!

The changes align with the new functionality of listing products.

packages/api/src/@core/connections/crm/crm.connection.module.ts (2)

23-23: LGTM!

The import statement for MicrosoftDynamicsSalesConnectionService is necessary for the new functionality.


48-48: LGTM!

The addition of MicrosoftDynamicsSalesConnectionService to the providers array is necessary for the new functionality.

packages/api/src/@core/connections/connections.controller.ts (2)

38-38: LGTM!

The enhancement to StateDataType adds flexibility to the state data structure.


85-92: LGTM!

The destructuring assignment of stateData now includes the resource property, aligning with the new functionality.

packages/shared/src/authUrl.ts (2)

58-61: LGTM! But verify the function usage in the codebase.

The code changes are approved.

However, ensure that all function calls to constructAuthUrl pass the additionalParams object when the provider is microsoftdynamicssales.

Tools
Biome

[error] 60-60: Forbidden non-null assertion.

Unsafe fix: Replace with optional chain operator ?. This operator includes runtime checks, so it is safer than the compile-only non-null assertion operator

(lint/style/noNonNullAssertion)


172-184: LGTM! But verify the function usage in the codebase.

The code changes are approved.

However, ensure that all function calls to handleOAuth2Url pass the additionalParams object when the provider is microsoftdynamicssales.

Verification successful

Verification successful: The additionalParams object is correctly populated and passed to handleOAuth2Url when the provider is microsoftdynamicssales.

  • The state object is updated to include additionalParams.end_user_domain as resource when the provider is microsoftdynamicssales.
  • This state object is then passed to handleOAuth2Url.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all function calls to `handleOAuth2Url` pass the `additionalParams` object when the provider is `microsoftdynamicssales`.

# Test: Search for the function usage. Expect: Occurrences of the new signature.
rg --type typescript -A 5 $'handleOAuth2Url'

Length of output: 78


Script:

#!/bin/bash
# Description: Verify all function calls to `handleOAuth2Url` pass the `additionalParams` object when the provider is `microsoftdynamicssales`.

# Find all TypeScript files and search for `handleOAuth2Url` within those files.
fd --extension ts --exec rg 'handleOAuth2Url'

Length of output: 136


Script:

#!/bin/bash
# Description: Verify all function calls to `handleOAuth2Url` pass the `additionalParams` object when the provider is `microsoftdynamicssales`.

# Find all TypeScript files and search for `handleOAuth2Url` within those files, including more context lines for better understanding.
fd --extension ts --exec rg 'handleOAuth2Url' -A 10 -B 5

Length of output: 751


Script:

#!/bin/bash
# Description: Verify that `additionalParams` is correctly populated and passed to `handleOAuth2Url` when the provider is `microsoftdynamicssales`.

# Find all TypeScript files and search for `additionalParams` within those files, including more context lines for better understanding.
fd --extension ts --exec rg 'additionalParams' -A 10 -B 10

Length of output: 6113

Tools
Biome

[error] 181-181: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 182-182: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)

packages/shared/src/connectors/metadata.ts (6)

213-213: Update logo path.

The logoPath has been updated to a new URL. Ensure that the new logo is correctly displayed and the URL is accessible.

Verification successful

The new logo URL is accessible and returns an HTTP/2 200 status code. The update to the logoPath is correctly implemented.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the accessibility of the new logo URL.

# Test: Check if the new logo URL is accessible.
curl -I 'https://play-lh.googleusercontent.com/MC_Aoa7rlMjGtcgAdiLJGeIm3-kpVw7APQmQUrUZtXuoZokiqVOJqR-bTu7idJBD8g' | grep 'HTTP/2 200'

Length of output: 463


206-206: Ensure consistent naming conventions.

The connector key has been changed from 'microsoft_dynamics_sales' to 'microsoftdynamicssales'. Ensure that this change is reflected consistently throughout the codebase to avoid any discrepancies.

Verification successful

Consistent naming conventions verified.

The connector key has been updated to microsoftdynamicssales and is used consistently throughout the codebase.

  • No occurrences of the old key microsoft_dynamics_sales were found.
  • The new key microsoftdynamicssales is present in all relevant files.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify consistent usage of the new connector key `microsoftdynamicssales`.

# Test: Search for the old and new connector keys. Expect: No occurrences of the old key, only the new key should be present.
rg --type js --type ts 'microsoft_dynamics_sales'
rg --type js --type ts 'microsoftdynamicssales'

Length of output: 1659


220-220: Modernize authentication strategy.

The authStrategy has shifted from AuthStrategy.api_key to AuthStrategy.oauth2, which is a more secure and modern approach. Ensure that all relevant parts of the codebase are updated to handle OAuth2 authentication.


210-210: Verify dynamic URL generation.

The authBaseUrl now uses a template string incorporating the orgName parameter. Ensure that orgName is correctly provided and sanitized to prevent any security issues.


216-218: Validate new options.

The options property now includes end_user_domain: true. Ensure that this option is correctly handled in the codebase and does not introduce any security vulnerabilities.


211-211: Update API version.

The apiUrl has been set to '/api/data/v9.2'. Ensure that all API calls are compatible with this version and update any documentation or references to the API version accordingly.

@@ -4,7 +4,7 @@ description: "Read data from multiple Ecommerce platforms using a single API"
icon: "star"
---

## List files in a Ecommerce provider using Panora
## List products in a Ecommerce provider using Panora
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix grammatical issue.

Use "an" instead of "a" before "Ecommerce provider".

- ## List products in a Ecommerce provider using Panora
+ ## List products in an Ecommerce provider using Panora
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## List products in a Ecommerce provider using Panora
## List products in an Ecommerce provider using Panora
Tools
LanguageTool

[misspelling] ~7-~7: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ..." icon: "star" --- ## List products in a Ecommerce provider using Panora <Check...

(EN_A_VS_AN)

'microsoft_dynamics_sales': {
scopes: '',
'microsoftdynamicssales': {
scopes: 'offline_access',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a more descriptive scope.

The scope 'offline_access' has been added. While this is correct, consider adding more specific scopes that align with the permissions required by the Microsoft Dynamics Sales API for better security and functionality.

- scopes: 'offline_access',
+ scopes: 'offline_access Dynamics.CRM.read Dynamics.CRM.write',
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
scopes: 'offline_access',
scopes: 'offline_access Dynamics.CRM.read Dynamics.CRM.write',

Comment on lines +179 to +182
let b = `https://${resource}/.default`;
b += (' offline_access');
console.log("scopes is "+ b)
console.log("BASE URL is "+ BASE_URL)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use template literals for string concatenation.

Template literals are preferred over string concatenation for better readability.

-      let b = `https://${resource}/.default`;
-      b += (' offline_access'); 
-      console.log("scopes is "+ b)
-      console.log("BASE URL is "+ BASE_URL)
+      let b = `https://${resource}/.default offline_access`;
+      console.log(`scopes is ${b}`);
+      console.log(`BASE URL is ${BASE_URL}`);
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
let b = `https://${resource}/.default`;
b += (' offline_access');
console.log("scopes is "+ b)
console.log("BASE URL is "+ BASE_URL)
let b = `https://${resource}/.default offline_access`;
console.log(`scopes is ${b}`);
console.log(`BASE URL is ${BASE_URL}`);
Tools
Biome

[error] 181-181: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 182-182: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)

const state = encodeURIComponent(JSON.stringify({ projectId, linkedUserId, providerName, vertical, returnUrl }));
let state = encodeURIComponent(JSON.stringify({ projectId, linkedUserId, providerName, vertical, returnUrl }));
if (providerName == 'microsoftdynamicssales') {
state = encodeURIComponent(JSON.stringify({ projectId, linkedUserId, providerName, vertical, returnUrl, resource: additionalParams!.end_user_domain }));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Avoid non-null assertion.

Using non-null assertion (!) can lead to runtime errors. Replace it with optional chaining (?.) to ensure safety.

-    state = encodeURIComponent(JSON.stringify({ projectId, linkedUserId, providerName, vertical, returnUrl, resource: additionalParams!.end_user_domain }));
+    state = encodeURIComponent(JSON.stringify({ projectId, linkedUserId, providerName, vertical, returnUrl, resource: additionalParams?.end_user_domain }));
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
state = encodeURIComponent(JSON.stringify({ projectId, linkedUserId, providerName, vertical, returnUrl, resource: additionalParams!.end_user_domain }));
state = encodeURIComponent(JSON.stringify({ projectId, linkedUserId, providerName, vertical, returnUrl, resource: additionalParams?.end_user_domain }));
Tools
Biome

[error] 60-60: Forbidden non-null assertion.

Unsafe fix: Replace with optional chain operator ?. This operator includes runtime checks, so it is safer than the compile-only non-null assertion operator

(lint/style/noNonNullAssertion)

});
this.logger.log('OAuth credentials updated : microsoftdynamicssales ');
} catch (error) {
throw error;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove redundant catch clause.

The catch clause that only rethrows the original error is redundant and can be removed.

-    } catch (error) {
-      throw error;
-    }
+    }
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
throw error;
}
Tools
Biome

[error] 240-240: The catch clause that only rethrows the original error is redundant.

These unnecessary catch clauses can be confusing. It is recommended to remove them.

(lint/complexity/noUselessCatch)

config.linkedUserId,
);
} catch (error) {
throw error;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove redundant catch clause.

The catch clause that only rethrows the original error is redundant and can be removed.

-    } catch (error) {
-      throw error;
-    }
+    }
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
throw error;
}
Tools
Biome

[error] 93-93: The catch clause that only rethrows the original error is redundant.

These unnecessary catch clauses can be confusing. It is recommended to remove them.

(lint/complexity/noUselessCatch)

}
return db_res;
} catch (error) {
throw error;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove redundant catch clause.

The catch clause that only rethrows the original error is redundant and can be removed.

-    } catch (error) {
-      throw error;
-    }
+    }
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
throw error;
}
Tools
Biome

[error] 189-189: The catch clause that only rethrows the original error is redundant.

These unnecessary catch clauses can be confusing. It is recommended to remove them.

(lint/complexity/noUselessCatch)

Comment on lines +134 to +135
'OAuth credentials : microsoftdynamicssales crm ' +
JSON.stringify(data),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use template literals for string concatenation.

Template literals are preferred over string concatenation for better readability.

-        'OAuth credentials : microsoftdynamicssales crm ' +
-          JSON.stringify(data),
+        `OAuth credentials : microsoftdynamicssales crm ${JSON.stringify(data)}`,
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
'OAuth credentials : microsoftdynamicssales crm ' +
JSON.stringify(data),
`OAuth credentials : microsoftdynamicssales crm ${JSON.stringify(data)}`,
Tools
Biome

[error] 134-135: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)

import axios from 'axios';
import { v4 as uuidv4 } from 'uuid';
import { ServiceRegistry } from '../registry.service';
import { URLSearchParams } from 'url';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use node: protocol for Node.js built-in modules.

Using the node: protocol is more explicit and signals that the imported module belongs to Node.js.

- import { URLSearchParams } from 'url';
+ import { URLSearchParams } from 'node:url';
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
import { URLSearchParams } from 'url';
import { URLSearchParams } from 'node:url';
Tools
Biome

[error] 25-25: A Node.js builtin module should be imported with the node: protocol.

Using the node: protocol is more explicit and signals that the imported module belongs to Node.js.
Unsafe fix: Add the node: protocol.

(lint/style/useNodejsImportProtocol)

@naelob naelob merged commit bc00593 into main Aug 7, 2024
11 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants