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

chore: Proper use enum in checking new version #1123

Merged
merged 3 commits into from
Jul 5, 2024
Merged

Conversation

Czaki
Copy link
Collaborator

@Czaki Czaki commented Jul 4, 2024

Summary by CodeRabbit

  • Bug Fixes

    • Improved version information display with updated message box configurations.
  • Refactor

    • Restructured MockMessageBox class for better organization of constants.

@Czaki Czaki added this to the 0.15.3 milestone Jul 4, 2024
Copy link
Contributor

coderabbitai bot commented Jul 4, 2024

Walkthrough

The changes involve updating message box configurations and restructuring the mock message box class for better organization. Specifically, QMessageBox.Information and QMessageBox.Ok | QMessageBox.Ignore constants were replaced with their StandardButton equivalents in check_version.py. The MockMessageBox in test_check_release.py was restructured to include nested classes for better organization of constants.

Changes

File(s) Change Summary
package/PartSeg/_launcher/check_version.py Updated message box usage from QMessageBox.Information and `QMessageBox.Ok
package/tests/test_PartSeg/test_check_release.py Restructured MockMessageBox class to include nested StandardButton and Icon classes for organizing constants.

Poem

The message box has found its tune,
With StandardButton buttons, oh so soon.
Organized mocks with structured grace,
Now tests run smoother, a joyful race.
🐰✨ Cheers to code that's clean and bright,
Great changes made, it's quite the sight! 🌟


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

sourcery-ai bot commented Jul 4, 2024

🧙 Sourcery has finished reviewing your pull request!


Tips
  • Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
  • Continue your discussion with Sourcery by replying directly to review comments.
  • You can change your review settings at any time by accessing your dashboard:
    • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
    • Change the review language;
  • You can always contact us if you have any questions or feedback.

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

We've reviewed this pull request using the Sourcery rules engine. If you would also like our AI-powered code review then let us know.

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 5854740 and c997bb0.

Files selected for processing (1)
  • package/PartSeg/_launcher/check_version.py (1 hunks)
Additional comments not posted (5)
package/PartSeg/_launcher/check_version.py (5)

72-77: Use of QMessageBox.Icon.Information is correct.

The change from QMessageBox.Information to QMessageBox.Icon.Information is correct and aligns with PyQt5/PySide2 conventions.


77-77: Use of QMessageBox.StandardButton.Ok | QMessageBox.StandardButton.Ignore is correct.

The change from QMessageBox.Ok | QMessageBox.Ignore to QMessageBox.StandardButton.Ok | QMessageBox.StandardButton.Ignore is correct and aligns with PyQt5/PySide2 conventions.


81-86: Use of QMessageBox.StandardButton.Information is correct.

The change from QMessageBox.Information to QMessageBox.StandardButton.Information is correct and aligns with PyQt5/PySide2 conventions.


86-86: Use of QMessageBox.StandardButton.Ignore is correct.

The change from QMessageBox.Ignore to QMessageBox.StandardButton.Ignore is correct and aligns with PyQt5/PySide2 conventions.


89-89: Correct usage of QMessageBox.StandardButton.Ignore in the condition.

The change from QMessageBox.Ignore to QMessageBox.StandardButton.Ignore in the condition is correct and aligns with PyQt5/PySide2 conventions.

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 c997bb0 and 0274c12.

Files selected for processing (2)
  • package/PartSeg/_launcher/check_version.py (1 hunks)
  • package/tests/test_PartSeg/test_check_release.py (1 hunks)
Additional comments not posted (7)
package/PartSeg/_launcher/check_version.py (5)

72-77: Correct use of QMessageBox.Icon.Information.

The change from QMessageBox.Information to QMessageBox.Icon.Information is correct and follows the updated API.


77-77: Correct use of QMessageBox.StandardButton.Ok | QMessageBox.StandardButton.Ignore.

The change from QMessageBox.Ok | QMessageBox.Ignore to QMessageBox.StandardButton.Ok | QMessageBox.StandardButton.Ignore is correct and follows the updated API.


81-86: Correct use of QMessageBox.Icon.Information.

The change from QMessageBox.Information to QMessageBox.Icon.Information is correct and follows the updated API.


86-86: Correct use of QMessageBox.StandardButton.Ok | QMessageBox.StandardButton.Ignore.

The change from QMessageBox.Ok | QMessageBox.Ignore to QMessageBox.StandardButton.Ok | QMessageBox.StandardButton.Ignore is correct and follows the updated API.


89-89: Correct use of QMessageBox.StandardButton.Ignore.

The change from QMessageBox.Ignore to QMessageBox.StandardButton.Ignore is correct and follows the updated API.

package/tests/test_PartSeg/test_check_release.py (2)

46-50: Correct restructuring of MockMessageBox.StandardButton.

The restructuring of MockMessageBox to include the nested class StandardButton with constants Information, Ok, and Ignore is correct and improves organization.


51-52: Correct restructuring of MockMessageBox.Icon.

The restructuring of MockMessageBox to include the nested class Icon with the constant Information is correct and improves organization.

Copy link

sonarcloud bot commented Jul 5, 2024

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 0274c12 and 3465c37.

Files selected for processing (1)
  • package/tests/test_PartSeg/test_check_release.py (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • package/tests/test_PartSeg/test_check_release.py

Copy link

codecov bot commented Jul 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.93%. Comparing base (5854740) to head (3465c37).
Report is 79 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1123      +/-   ##
===========================================
+ Coverage    92.91%   92.93%   +0.01%     
===========================================
  Files          205      205              
  Lines        32519    32519              
===========================================
+ Hits         30215    30220       +5     
+ Misses        2304     2299       -5     

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

@Czaki Czaki merged commit 2e64542 into develop Jul 5, 2024
51 checks passed
@Czaki Czaki deleted the update_dialog_qt_fix branch July 5, 2024 07:51
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.

1 participant