Changes to published stub

[15g-lucas]

The stub control.stub was published under the name “controller.stub”.
However, controller.stub corresponds to the Laravel stub for controllers, creating an inconsistency.

I renamed it to control.stub

Summary by CodeRabbit

• Bug Fixes
  • Corrected the registration key for the control stub to match its actual filename, ensuring proper stub usage.
• Tests
  • Updated test assertions to reflect the corrected stub filename, improving test accuracy.

[coderabbitai]

Walkthrough

The changes correct a mismatch in the stub registration key within the AccessServiceProvider class, updating it from 'controller.stub' to 'control.stub' to match the actual filename. Correspondingly, the related unit test is updated to expect the correct stub name. No other logic, control flow, or exported/public entity declarations are modified.

Changes

File(s)	Change Summary
src/AccessServiceProvider.php	Fixed the stub registration key from 'controller.stub' to 'control.stub' in registerStubs.
tests/Unit/StubsTest.php	Updated test assertion to expect 'control.stub' instead of 'controller.stub'.

Poem

In the warren of code, a stub found its name,
No longer controller, but control it became.
The tests now align, all errors are gone,
With keys and with carrots, we code right along.
🥕

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dd5890b and 6f807b9.

📒 Files selected for processing (2)

• src/AccessServiceProvider.php (1 hunks)
• tests/Unit/StubsTest.php (1 hunks)

🔇 Additional comments (2)

src/AccessServiceProvider.php (1)

89-89: Corrected stub registration key to match the actual filename

The change fixes a naming inconsistency where the stub file named "control.stub" was incorrectly registered as "controller.stub". This alignment prevents confusion with Laravel's default controller stub and ensures the published stub has a name consistent with its purpose.

tests/Unit/StubsTest.php (1)

15-15: Correctly updated test expectation to match the stub naming correction

The test assertion has been properly updated to expect 'control.stub' instead of 'controller.stub', ensuring consistency with the change made in the AccessServiceProvider. This update maintains the test's validity after the service provider fix.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.