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

Method chaining must be fully multiline, with the first item on a new line #7793

Open
Tracked by #7247
mvorisek opened this issue Jan 31, 2024 · 2 comments
Open
Tracked by #7247

Comments

@mvorisek
Copy link
Contributor

mvorisek commented Jan 31, 2024

Feature request

extracted from #7247

expected output:

 <?php

-$foo->a()->b()->c();
+$foo
+    ->a()
+    ->b()
+    ->c();

helpful also for coverage measurements

@Wirone
Copy link
Member

Wirone commented Jan 31, 2024

I've linked this issue in the todo list of #7247 but please don't extract other items to dedicated issues. PER-CS support doesn't need to be provided at once (rather PR per todo list item), but also atomic PRs don't need atomic issues, and can be referenced to the main one. Some todo items have issues/PRs linked because these were already created. Creating new ones will only cause more maintenance burden (stale bot) and will increase the size of the backlog.

Copy link

Since this issue has not had any activity within the last 90 days, I have marked it as stale.

The purpose of this action is to enforce backlog review once in a while. This is mostly for maintainers and helps with keeping repository in good condition, because stale issues and PRs can accumulate over time and make it harder for others to find relevant information. It is also possible that some changes has been made to the repo already, and issue or PR became outdated, but wasn't closed for some reason. This action helps with periodic review and closing of such stale items in automated way.

You may let maintainers handle this or verify current relevancy by yourself, to help with re-triage. Any activity will remove stale label so it won't be automatically closed at this point.

I will close it if no further activity occurs within the next 30 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants