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 documentation links #10

Merged
merged 2 commits into from
Feb 19, 2024
Merged

Fix documentation links #10

merged 2 commits into from
Feb 19, 2024

Conversation

msmakouz
Copy link
Member

@msmakouz msmakouz commented Feb 7, 2024

Q A
Bugfix?
Breaks BC?
New feature?
  • Need to fix tests

What's changed

  1. Updated version of roadrunner-php/roadrunner-api-dto
  2. Fixed unit test (replaced \RoadRunner\Shared\DTO\V1\Status with \RoadRunner\Common\DTO\V1\Status)
  3. Updated documentation link

@msmakouz msmakouz added the documentation Improvements or additions to documentation label Feb 7, 2024
@msmakouz msmakouz requested a review from rustatian February 7, 2024 18:16
@msmakouz msmakouz self-assigned this Feb 7, 2024
Copy link

coderabbitai bot commented Feb 7, 2024

Walkthrough

This update introduces adjustments to the PHP version configurations and removes the master branch restriction in the GitHub workflow files. Additionally, it updates a URL link within the README.md for managing Roadrunner services and refreshes the documentation link for the create method in Manager.php. These changes streamline development workflows and ensure up-to-date resources are referenced.

Changes

Files Change Summaries
.github/workflows/... Adjusted PHP version configuration, removed master branch restriction
README.md Updated URL link for Roadrunner services management
src/Manager.php Updated documentation link for the create method

🐇✨
In the land of code and byte,
Changes come both day and night.
With each update, we leap and bound,
Making our code more profound. 🚀🌟

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-tests for this file.
  • 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 tests 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 from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@msmakouz msmakouz marked this pull request as draft February 7, 2024 18:18
Copy link

@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.

Review Status

Actionable comments generated: 5

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 9b5cdb6 and e2be18c.
Files ignored due to path filters (1)
  • composer.json is excluded by: !**/*.json
Files selected for processing (4)
  • .github/workflows/phpunit.yml (2 hunks)
  • .github/workflows/psalm.yml (2 hunks)
  • README.md (1 hunks)
  • src/Manager.php (1 hunks)
Additional comments: 4
.github/workflows/psalm.yml (1)
  • 6-6: Setting pull_request: null disables pull request events. Ensure this is intentional, as it might limit workflow triggers for PRs.
.github/workflows/phpunit.yml (1)
  • 6-6: Setting pull_request: null disables pull request events. Ensure this is intentional, as it might limit workflow triggers for PRs.
README.md (1)
  • 9-9: The updated URL link is correctly formatted and points to the intended documentation page. This change aligns with the PR objectives.
src/Manager.php (1)
  • 67-67: The updated URL link in the docblock is correctly formatted and points to the intended documentation page. This change aligns with the PR objectives.

Comment on lines 3 to 4
branches:
- master
- '*.*'
Copy link

Choose a reason for hiding this comment

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

The branch wildcard pattern '*.*' might not match all branches, especially those without a dot. Consider using '**' to include all branches if that's the intention.

Comment on lines 12 to 14
with:
os: >-
['ubuntu-latest']
Copy link

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [11-13]

The os configuration is specified as an array but should be a string for a single value. Remove the array notation.

-        ['ubuntu-latest']
+        ubuntu-latest

Comment on lines 3 to 4
branches:
- master
- '*.*'
Copy link

Choose a reason for hiding this comment

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

The branch wildcard pattern '*.*' might not match all branches, especially those without a dot. Consider using '**' to include all branches if that's the intention.

Comment on lines 12 to 16
with:
os: >-
['ubuntu-latest']
php: >-
['8.1', '8.2']
stability: >-
['prefer-stable']
Copy link

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [11-13]

The os configuration is specified as an array but should be a string for a single value. Remove the array notation.

-        ['ubuntu-latest']
+        ubuntu-latest

Comment on lines 14 to 16
['ubuntu-latest']
php: >-
['8.1', '8.2']
stability: >-
['prefer-stable']
Copy link

Choose a reason for hiding this comment

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

The stability configuration is specified as an array but should be a string for a single value. Remove the array notation.

-        ['prefer-stable']
+        prefer-stable

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.

Suggested change
['ubuntu-latest']
php: >-
['8.1', '8.2']
stability: >-
['prefer-stable']
['ubuntu-latest']
stability: >-
prefer-stable

@msmakouz msmakouz marked this pull request as ready for review February 19, 2024 14:31
Copy link

codecov bot commented Feb 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (9b5cdb6) 92.42% compared to head (13bb24c) 92.42%.
Report is 1 commits behind head on 2.x.

Additional details and impacted files
@@            Coverage Diff            @@
##                2.x      #10   +/-   ##
=========================================
  Coverage     92.42%   92.42%           
  Complexity       15       15           
=========================================
  Files             1        1           
  Lines            66       66           
=========================================
  Hits             61       61           
  Misses            5        5           

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

Copy link

@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.

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between e2be18c and 13bb24c.
Files ignored due to path filters (1)
  • composer.json is excluded by: !**/*.json
Files selected for processing (1)
  • tests/ManagerTest.php (1 hunks)
Additional comments: 2
tests/ManagerTest.php (2)
  • 191-191: The namespace for the Status object instantiation has been updated from \RoadRunner\Shared\DTO\V1\Status to \RoadRunner\Common\DTO\V1\Status. This change aligns with the PR's objective to fix documentation links and possibly reorganize project structure for clarity. Ensure that all references to the Status class throughout the project have been updated to reflect this new namespace to maintain consistency and avoid potential issues with class resolution.
Verification successful

The namespace update from \RoadRunner\Shared\DTO\V1\Status to \RoadRunner\Common\DTO\V1\Status in tests/ManagerTest.php appears to be correctly applied, with no occurrences of the old namespace found in the project's PHP files. This change is consistent with the provided context. However, given that the new namespace is referenced only once in the provided output, it's recommended to ensure that all necessary references to the Status class throughout the project have been updated to reflect this new namespace. This broader review is essential for maintaining consistency and avoiding potential issues with class resolution across the entire project.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Search for old namespace usage to ensure it's fully replaced.
rg --type php '\\RoadRunner\\Shared\\DTO\\V1\\Status'
# Search for new namespace usage to confirm consistency.
rg --type php '\\RoadRunner\\Common\\DTO\\V1\\Status'

Length of output: 212

* 188-194: > 📝 **NOTE** > This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [1-193]

Overall, the test file tests/ManagerTest.php is well-structured and follows good testing practices. The update to the namespace for the Status object instantiation is correctly applied within the context of this file. Ensure that similar updates are consistently applied across the project where necessary. The test methods are clear, focused, and effectively isolate the class under test from external dependencies. This contributes to the maintainability and reliability of the test suite.

@msmakouz msmakouz merged commit 362208a into 2.x Feb 19, 2024
6 checks passed
@msmakouz msmakouz deleted the docs branch February 19, 2024 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants