fix: prefix all functions with back-slash

[lotyp]

Summary by CodeRabbit

• Improvements
  • Enhanced the rule set to apply more broadly by changing the scope parameter from 'namespaced' to 'all'. This allows for more comprehensive rule application across different contexts.

[coderabbitai]

Walkthrough

The primary change in this update involves modifying the 'scope' parameter within the rules method of the ExtendedPERSet class from 'namespaced' to 'all'. This alteration broadens the applicability of the rules, allowing them to be applied globally rather than being confined to a specific namespace.

Changes

File	Change Summary
src/RuleSets/ExtendedPERSet.php	Changed 'scope' parameter in rules method from 'namespaced' to 'all'.

Poem

In the code where rules reside,
Scope was changed, now open wide.
From 'namespaced' to 'all' they flow,
Universal paths to show.
Boundaries fade, horizons clear,
Code evolves, new frontiers near.
🐇✨

---

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

• 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>.
  • 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 full the 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.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 56.37%. Comparing base (7c9e56d) to head (cf83942).

Files	Patch %	Lines
src/RuleSets/ExtendedPERSet.php	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff            @@
##             master     #283   +/-   ##
=========================================
  Coverage     56.37%   56.37%           
  Complexity       19       19           
=========================================
  Files             3        3           
  Lines           243      243           
=========================================
  Hits            137      137           
  Misses          106      106           

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

[coderabbitai]

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 7c9e56d and cf83942.

Files selected for processing (1)

• src/RuleSets/ExtendedPERSet.php (1 hunks)

Additional Context Used

GitHub Check Runs (1)

codecov/patch failure (1)

src/RuleSets/ExtendedPERSet.php: [warning] 94-94: src/RuleSets/ExtendedPERSet.php#L94
Added line #L94 was not covered by tests

Additional comments not posted (1)

src/RuleSets/ExtendedPERSet.php (1)

94-94: The change in scope from 'namespaced' to 'all' significantly broadens the impact of the ruleset. Ensure that this change is intentional and well-documented to avoid unexpected behavior in broader contexts.

[coderabbitai]

This line is not covered by tests. It's crucial to ensure that changes, especially those that affect the behavior of the system broadly, are well-tested.

Would you like me to help by generating unit tests for this change or should I open a GitHub issue to track this task?