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

fix: package lint issues #1773

Merged
merged 4 commits into from
Jul 1, 2024
Merged

Conversation

saikumarrs
Copy link
Member

@saikumarrs saikumarrs commented Jun 30, 2024

PR Description

I've addressed all the linting issues in the packages.

Fixes:
#1757

Linear task (optional)

https://linear.app/rudderstack/issue/SDK-2052/investigate-github-issue

Cross Browser Tests

Please confirm you have tested for the following browsers:

  • Chrome
  • Firefox
  • IE11

Sanity Suite

  • All sanity suite test cases pass locally

Security

  • The code changed/added as part of this pull request won't create any security issues with how the software is being used.

Summary by CodeRabbit

  • Chores

    • Added linting checks to the workflow for improved security, code quality, and bundle size management.
    • Defined size limits for various modules, ensuring optimized package size for better performance.
    • Updated file extensions and export syntax across multiple configuration files for consistency and improved build processes.
    • Adjusted size limits for legacy builds to enhance performance and reduce load times.
  • Refactor

    • Improved import paths to use package aliases, streamlining the codebase and reducing complexities.

@saikumarrs saikumarrs self-assigned this Jun 30, 2024
Copy link
Contributor

coderabbitai bot commented Jun 30, 2024

Walkthrough

These changes primarily focus on improving the build process, enforcing size limits for various packages, and updating code quality checks. Specific modifications include transitioning JavaScript files to use modern ESM and CJS formats, refining Rollup configurations for accurate builds, and adjusting size limits for more precise control over package sizes. Additionally, some import paths and utility scripts were updated for better maintainability and consistency.

Changes

File(s) Summary
.github/workflows/security-code-quality-and-bundle-size-checks.yml Added a step to execute package linting checks in the workflow for security, code quality, and bundle size checks.
packages/.../analytics-js-cookies/.size-limit.mjs Defined size limits for different modules related to Cookies Utilities in ESM and CJS formats for NPM packages.
packages/.../analytics-js-cookies/rollup.config.mjs Updated entry and output file extensions, and modified the build process for TypeScript definitions.
packages/.../analytics-js-plugins/.size-limit.mjs Switched from module.exports to export default for the export syntax.
packages/.../analytics-js-plugins/rollup.config.mjs Updated entry file names and output structure for build entries.
packages/.../analytics-js-service-worker/.size-limit.mjs Defined size limits for Service Worker modules in both ESM and CJS formats for NPM distribution.
packages/.../analytics-js-service-worker/rollup.config.mjs Added imports and configurations for different output file formats, updated plugins, and output paths for .d.ts files.
packages/.../analytics-js/.size-limit.mjs Updated file extensions and size limits in the .size-limit.mjs file.
packages/.../analytics-js/rollup.config.mjs Updated entry file names for output files and modified output configurations for TypeScript definitions.
packages/.../analytics-v1.1/__tests__/utils/navigator.test.js Updated the import path for the BraveBrowser module in the navigator.test.js file.
packages/.../analytics-js-integrations/.size-limit.js Adjusted the size limit for the "All Integrations (legacy build) - CDN".
packages/.../analytics-js-integrations/scripts/integrationBuildScript.js Updated the import path for a utility function to use a package alias.

Tip

Early access features: enabled

We are currently testing the following features in early access:

  • OpenAI gpt-4o model for code reviews and chat: OpenAI claims that this model is better at understanding and generating code than the previous models. We seek your feedback over the next few weeks before making it generally available.

Note:

  • You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
  • Please join our Discord Community to provide feedback and report issues.
  • OSS projects are currently opted into early access features by default.

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 Configration 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: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 40ba82e and f4b488d.

Files ignored due to path filters (8)
  • nx.json is excluded by !**/*.json
  • package-lock.json is excluded by !**/package-lock.json, !**/*.json
  • package.json is excluded by !**/*.json
  • packages/analytics-js-cookies/package.json is excluded by !**/*.json
  • packages/analytics-js-plugins/package.json is excluded by !**/*.json
  • packages/analytics-js-service-worker/package.json is excluded by !**/*.json
  • packages/analytics-js/package.json is excluded by !**/*.json
  • packages/sanity-suite/package.json is excluded by !**/*.json
Files selected for processing (10)
  • .github/workflows/security-code-quality-and-bundle-size-checks.yml (1 hunks)
  • packages/analytics-js-cookies/.size-limit.mjs (1 hunks)
  • packages/analytics-js-cookies/rollup.config.mjs (3 hunks)
  • packages/analytics-js-plugins/.size-limit.mjs (1 hunks)
  • packages/analytics-js-plugins/rollup.config.mjs (3 hunks)
  • packages/analytics-js-service-worker/.size-limit.mjs (1 hunks)
  • packages/analytics-js-service-worker/rollup.config.mjs (5 hunks)
  • packages/analytics-js/.size-limit.mjs (1 hunks)
  • packages/analytics-js/rollup.config.mjs (3 hunks)
  • packages/analytics-v1.1/tests/utils/navigator.test.js (1 hunks)
Files skipped from review due to trivial changes (6)
  • .github/workflows/security-code-quality-and-bundle-size-checks.yml
  • packages/analytics-js-cookies/.size-limit.mjs
  • packages/analytics-js-plugins/.size-limit.mjs
  • packages/analytics-js-service-worker/.size-limit.mjs
  • packages/analytics-js/.size-limit.mjs
  • packages/analytics-v1.1/tests/utils/navigator.test.js
Additional context used
Learnings (3)
packages/analytics-js-service-worker/rollup.config.mjs (1)
Learnt from: saikumarrs
PR: rudderlabs/rudder-sdk-js#1759
File: packages/analytics-js-cookies/rollup.config.mjs:1-20
Timestamp: 2024-06-25T08:25:30.628Z
Learning: User `saikumarrs` prefers to temporarily accept missing dependencies in `package.json` for `rollup.config.mjs` in the context of PR 1759 without immediate correction.
packages/analytics-js-cookies/rollup.config.mjs (1)
Learnt from: saikumarrs
PR: rudderlabs/rudder-sdk-js#1759
File: packages/analytics-js-cookies/rollup.config.mjs:1-20
Timestamp: 2024-06-25T08:25:30.628Z
Learning: User `saikumarrs` prefers to temporarily accept missing dependencies in `package.json` for `rollup.config.mjs` in the context of PR 1759 without immediate correction.
packages/analytics-js/rollup.config.mjs (1)
Learnt from: saikumarrs
PR: rudderlabs/rudder-sdk-js#1759
File: packages/analytics-js-cookies/rollup.config.mjs:1-20
Timestamp: 2024-06-25T08:25:30.628Z
Learning: User `saikumarrs` prefers to temporarily accept missing dependencies in `package.json` for `rollup.config.mjs` in the context of PR 1759 without immediate correction.
Biome
packages/analytics-js/rollup.config.mjs

[error] 70-72: This else clause can be omitted because previous branches break early.

Unsafe fix: Omit the else clause.

(lint/style/noUselessElse)

Additional comments not posted (9)
packages/analytics-js-service-worker/rollup.config.mjs (3)

16-17: New imports for del and alias plugins.

The addition of del and alias plugins is appropriate for managing file deletions and aliasing paths, respectively. Ensure that these plugins are listed in package.json.

Verification successful

New imports for del and alias plugins.

The addition of del and alias plugins is appropriate for managing file deletions and aliasing paths, respectively. These plugins are confirmed to be listed in package.json.

  • rollup-plugin-delete
  • @rollup/plugin-alias
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the existence of `del` and `alias` plugins in package.json.

# Test: Search for the plugins in the dependencies. Expect: Both plugins to be listed.
rg --files-with-matches 'rollup-plugin-delete|@rollup/plugin-alias' package.json

Length of output: 95


Line range hint 108-126: LGTM!

The new entry file names (index.mjs, index.cjs, index.js) align with modern module formats.

Ensure that the output directories and formats are correctly configured.

Verification successful

LGTM!

The output directories and formats are correctly configured:

  • outDir is set to dist/npm.
  • Formats include esm, cjs, umd, and es.
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the correctness of output configurations.

# Test: Search for the output directories and formats. Expect: Correct configurations.
rg --files-with-matches 'outDir|format' packages/analytics-js-service-worker/rollup.config.mjs

Length of output: 151



Script:

#!/bin/bash
# Description: Extract lines containing 'outDir' and 'format' for detailed inspection.

# Extract and display lines with 'outDir' and 'format' in the specified file.
rg 'outDir|format' packages/analytics-js-service-worker/rollup.config.mjs

Length of output: 431


164-172: LGTM!

The new output paths for .d.ts files (index.d.mts, index.d.cts) align with modern TypeScript module formats.

Ensure that the output paths are correctly configured.

Verification successful

LGTM!

The new output paths for .d.ts files (index.d.mts, index.d.cts) align with modern TypeScript module formats and are correctly configured.

  • Correct configurations found in packages/analytics-js-service-worker/rollup.config.mjs around lines 164-172.
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the correctness of output paths.

# Test: Search for the output paths. Expect: Correct configurations.
rg --files-with-matches 'output|file' packages/analytics-js-service-worker/rollup.config.mjs

Length of output: 149



Script:

#!/bin/bash
# Description: Extract and display the relevant portions of the rollup.config.mjs file where `file` and `output` are configured.

# Extract lines containing 'output' or 'file' and display the surrounding context for better understanding.
rg 'output|file' -C 3 packages/analytics-js-service-worker/rollup.config.mjs

Length of output: 1327

packages/analytics-js-cookies/rollup.config.mjs (2)

Line range hint 107-117: LGTM!

The new entry file names (index.mjs, index.cjs) align with modern module formats.

Ensure that the output directories and formats are correctly configured.

Verification successful

LGTM!

The output directories and formats are correctly configured. The new entry file names (index.mjs, index.cjs) align with modern module formats, and the output paths and formats are appropriately set.

  • esm format is directed to dist/npm/esm/
  • cjs format is directed to dist/npm/cjs/
  • umd format is directed to dist/npm/umd/
  • Declaration files are using the es format.
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the correctness of output configurations.

# Test: Search for the output directories and formats. Expect: Correct configurations.
rg --files-with-matches 'outDir|format' packages/analytics-js-cookies/rollup.config.mjs

Length of output: 137



Script:

#!/bin/bash
# Extract lines containing 'outDir' and 'format' to verify their configurations
rg 'outDir|format' packages/analytics-js-cookies/rollup.config.mjs

Length of output: 438


165-173: LGTM!

The new output paths for .d.ts files (index.d.mts, index.d.cts) align with modern TypeScript module formats.

Ensure that the output paths are correctly configured.

Verification successful

LGTM!

The new output paths for .d.ts files (index.d.mts, index.d.cts) align with modern TypeScript module formats and are correctly configured in the rollup.config.mjs file.

  • Lines 165-173 in packages/analytics-js-cookies/rollup.config.mjs confirm the correct configuration.
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the correctness of output paths.

# Test: Search for the output paths. Expect: Correct configurations.
rg --files-with-matches 'output|file' packages/analytics-js-cookies/rollup.config.mjs

Length of output: 135



Script:

#!/bin/bash
# Extract and display lines 160-180 from the rollup.config.mjs file to verify the output paths configuration.
sed -n '160,180p' packages/analytics-js-cookies/rollup.config.mjs

Length of output: 411

packages/analytics-js-plugins/rollup.config.mjs (2)

Line range hint 155-165: LGTM!

The new entry file names (index.mjs, index.cjs) align with modern module formats.

Ensure that the output directories and formats are correctly configured.

Verification successful

Output configurations verified

The output directories and formats are correctly configured:

  • ESM format is set for outDirNpm + '/esm/' and outDirCDN.

  • CJS format is set for outDirNpm + '/cjs'.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the correctness of output configurations.

# Test: Search for the output directories and formats. Expect: Correct configurations.
rg --files-with-matches 'outDir|format' packages/analytics-js-plugins/rollup.config.mjs

Length of output: 137



Script:

#!/bin/bash
# Description: Extract configurations for output directories and formats.

# Extract lines containing 'outDir' and 'format' to verify their correctness.
rg 'outDir|format' packages/analytics-js-plugins/rollup.config.mjs

Length of output: 631


241-250: LGTM!

The new output paths for .d.ts files (index.d.mts, index.d.cts) align with modern TypeScript module formats.

Ensure that the output paths are correctly configured.

Verification successful

LGTM!

The new output paths for .d.ts files (index.d.mts, index.d.cts) align with modern TypeScript module formats.

  • packages/analytics-js-plugins/rollup.config.mjs lines 241-250:
    • ${outDirNpmRoot}/index.d.mts
    • ${outDirNpmRoot}/index.d.cts
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the correctness of output paths.

# Test: Search for the output paths. Expect: Correct configurations.
rg --files-with-matches 'output|file' packages/analytics-js-plugins/rollup.config.mjs

Length of output: 135



Script:

#!/bin/bash
# Extract lines 241-250 from the rollup.config.mjs file to verify output paths
sed -n '241,250p' packages/analytics-js-plugins/rollup.config.mjs

Length of output: 275

packages/analytics-js/rollup.config.mjs (2)

Line range hint 289-299: LGTM!

The new entry file names (index.mjs, index.cjs) align with modern module formats.

Ensure that the output directories and formats are correctly configured.

Verification successful

Output directories and formats are correctly configured.

The outDir and format settings for the new entry file names (index.mjs and index.cjs) align with the expected configurations for modern module formats.

  • index.mjs is configured with dir: outDirNpm + '/esm/' and format: 'esm'.
  • index.cjs is configured with dir: outDirNpm + '/cjs' and format: 'cjs'.
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the correctness of output configurations.

# Test: Search for the output directories and formats. Expect: Correct configurations.
rg --files-with-matches 'outDir|format' packages/analytics-js/rollup.config.mjs

Length of output: 121



Script:

#!/bin/bash
# Extract and display lines containing 'outDir' and 'format' configurations in the rollup.config.mjs file
rg 'outDir|format' packages/analytics-js/rollup.config.mjs -A 3 -B 3

Length of output: 2667


382-391: LGTM!

The new output paths for .d.ts files (index.d.mts, index.d.cts) align with modern TypeScript module formats.

Ensure that the output paths are correctly configured.

Verification successful

LGTM!

The new output paths for .d.ts files (index.d.mts, index.d.cts) align with modern TypeScript module formats and are correctly configured.

  • packages/analytics-js/rollup.config.mjs lines 382-391
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the correctness of output paths.

# Test: Search for the output paths. Expect: Correct configurations.
rg --files-with-matches 'output|file' packages/analytics-js/rollup.config.mjs

Length of output: 119



Script:

#!/bin/bash
# Description: Extract the specific configurations for output paths in rollup.config.mjs

# Use ast-grep to find the output configurations in the rollup config file
ast-grep --lang javascript --pattern $'output: [
  {
    file: $_,
    format: $_,
  },
  {
    file: $_,
    format: $_,
  }
]' packages/analytics-js/rollup.config.mjs

Length of output: 169



Script:

#!/bin/bash
# Description: Extract the specific configurations for output paths in rollup.config.mjs

# Use rg to find the output configurations in the rollup config file
rg 'output: \[' packages/analytics-js/rollup.config.mjs -A 10

Length of output: 279

Copy link

codecov bot commented Jun 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.26%. Comparing base (40ba82e) to head (b054ae7).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1773   +/-   ##
========================================
  Coverage    56.26%   56.26%           
========================================
  Files          467      467           
  Lines        15912    15912           
  Branches      3188     3177   -11     
========================================
  Hits          8953     8953           
- Misses        5717     5732   +15     
+ Partials      1242     1227   -15     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

coderabbitai[bot]
coderabbitai bot previously approved these changes Jun 30, 2024
Copy link

github-actions bot commented Jun 30, 2024

size-limit report 📦

Name Size (Base) Size (Current) Size Limit Status
Common Code - No bundling 15.83 KB 15.83 KB (0%) 16.5 KB
Cookies Utilities 1.6 KB 0 B (-100% ▼) null
Remote Module Federation Mapping - CDN 330 B 331 B (+0.31% ▲) 512 B
Remote Module Federated Plugins - CDN 5.74 KB 5.68 KB (-1.03% ▼) 6 KB
Core ESM - NPM 7.69 KB 7.66 KB (-0.42% ▼) 8 KB
Core CJS - NPM 23.65 KB 23.65 KB (0%) 24 KB
Core - NPM 23.74 KB 23.66 KB (-0.33% ▼) 24 KB
Core Legacy - CDN 44.47 KB 44.42 KB (-0.13% ▼) 45 KB
Core - CDN 23.93 KB 23.94 KB (+0.05% ▲) 24.5 KB
Core (legacy build) - CDN - v1.1 31.43 KB 31.43 KB (0%) 32 KB
Core - NPM - v1.1 31.45 KB 31.45 KB (0%) 32 KB
Service Worker Module 20.89 KB 0 B (-100% ▼) null
All Integrations (legacy build) - CDN 92.63 KB 92.63 KB (0%) 93 KB
Cookies Utilities ESM - NPM 0 B 0 B (+100% ▲) 2 KB
Cookies Utilities CJS - NPM 0 B 788 B (+100% ▲) 2 KB
Service Worker Module ESM - NPM 0 B 20.8 KB (+100% ▲) 24 KB
Service Worker Module CJS - NPM 0 B 20.95 KB (+100% ▲) 24 KB
Service Worker Module NPM 0 B 24.66 KB (+100% ▲) 25 KB

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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f4b488d and 38ddd34.

Files ignored due to path filters (10)
  • package.json is excluded by !**/*.json
  • packages/analytics-js-common/package.json is excluded by !**/*.json
  • packages/analytics-js-cookies/package.json is excluded by !**/*.json
  • packages/analytics-js-integrations/package.json is excluded by !**/*.json
  • packages/analytics-js-plugins/package.json is excluded by !**/*.json
  • packages/analytics-js-service-worker/package.json is excluded by !**/*.json
  • packages/analytics-js/package.json is excluded by !**/*.json
  • packages/analytics-v1.1/package.json is excluded by !**/*.json
  • packages/loading-scripts/package.json is excluded by !**/*.json
  • packages/sanity-suite/package.json is excluded by !**/*.json
Files selected for processing (3)
  • packages/analytics-js-integrations/.size-limit.js (1 hunks)
  • packages/analytics-js-integrations/scripts/integrationBuildScript.js (1 hunks)
  • packages/analytics-js-service-worker/.size-limit.mjs (1 hunks)
Files skipped from review due to trivial changes (1)
  • packages/analytics-js-integrations/.size-limit.js
Files skipped from review as they are similar to previous changes (1)
  • packages/analytics-js-service-worker/.size-limit.mjs
Additional comments not posted (1)
packages/analytics-js-integrations/scripts/integrationBuildScript.js (1)

5-5: Verify the alias configuration.

Ensure that the alias @rudderstack/analytics-js-common is correctly configured in the project's build system (e.g., tsconfig.json, webpack.config.js, etc.).

Verification successful

Alias configuration verified.

The alias @rudderstack/analytics-js-common is correctly configured in the project's build system, as evidenced by its presence in tsconfig.json and rollup.config.mjs. The extensive usage across the codebase further confirms its proper setup.

  • tsconfig.json: "@rudderstack/analytics-js-common/*": ["./packages/analytics-js-common/src/*"]
  • rollup.config.mjs: find: '@rudderstack/analytics-js-common'
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the alias configuration for @rudderstack/analytics-js-common.

# Test: Search for the alias configuration. Expect: Alias should be defined in the build system configuration files.
rg '@rudderstack/analytics-js-common'

Length of output: 141171

coderabbitai[bot]
coderabbitai bot previously approved these changes Jun 30, 2024
@saikumarrs saikumarrs marked this pull request as ready for review July 1, 2024 04:35
Copy link

sonarcloud bot commented Jul 1, 2024

@saikumarrs saikumarrs merged commit 8e45d05 into develop Jul 1, 2024
9 checks passed
@saikumarrs saikumarrs deleted the fix.implement-publint-issues-sdk-2052 branch July 1, 2024 08:41
@coderabbitai coderabbitai bot mentioned this pull request Jul 17, 2024
5 tasks
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.

2 participants