Skip to content

Conversation

@nfelt14
Copy link
Collaborator

@nfelt14 nfelt14 commented Nov 4, 2024

Proposed changes

chore: Update pyright dependency and use more reliable method of installing local nodejs for it

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Functionality update (non-breaking change which updates or changes existing functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • CI/CD update (an update to the CI/CD workflows, scripts, and/or configurations)
  • Documentation update (an update to enhance the user experience when reading through the docs)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have followed the guidelines in the CONTRIBUTING document
  • I have signed the CLA
  • I have checked to ensure there aren't other open Pull Requests for the same update/change
  • I have created (or updated) an Issue to track the status of this update/change and updated the link in this PR description (see above in the Proposed changes section) using the wording Addresses #<issue_number>
  • I have performed a self-review of my code
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • Basic linting passes locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have added necessary documentation (if appropriate)
  • I have updated the Changelog with a brief description of my changes

@nfelt14 nfelt14 requested a review from a team as a code owner November 4, 2024 18:07
@nfelt14 nfelt14 enabled auto-merge (squash) November 4, 2024 18:07
@codecov
Copy link

codecov bot commented Nov 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.59%. Comparing base (f3ada48) to head (590d875).
Report is 12 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #59   +/-   ##
=======================================
  Coverage   90.59%   90.59%           
=======================================
  Files          28       28           
  Lines        1797     1797           
  Branches      274      274           
=======================================
  Hits         1628     1628           
  Misses        106      106           
  Partials       63       63           

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

@github-actions
Copy link

github-actions bot commented Nov 4, 2024

Test Results (windows)

path passed subtotal
tests\test_tm_data_types.py 13 13
TOTAL 13 13

Link to workflow run

@github-actions
Copy link

github-actions bot commented Nov 4, 2024

Test Results (ubuntu)

path passed subtotal
tests/test_tm_data_types.py 13 13
TOTAL 13 13

Link to workflow run

@github-actions
Copy link

github-actions bot commented Nov 4, 2024

Test Results (macos)

path passed subtotal
tests/test_tm_data_types.py 13 13
TOTAL 13 13

Link to workflow run

@nfelt14 nfelt14 merged commit 41cda60 into main Nov 4, 2024
65 checks passed
@nfelt14 nfelt14 deleted the nfelt14/update-pyright branch November 4, 2024 22:44
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