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

Cleanup #257

Merged
merged 5 commits into from
Jun 22, 2024
Merged

Cleanup #257

merged 5 commits into from
Jun 22, 2024

Conversation

samdark
Copy link
Member

@samdark samdark commented Jun 19, 2024

Q A
Is bugfix?
New feature?
Breaks BC?

@samdark samdark requested review from vjik and xepozz June 19, 2024 20:35
src/Collector/ProxyLogTrait.php Outdated Show resolved Hide resolved
DebugResetCommand::COMMAND_NAME => DebugResetCommand::class,
DebugContainerCommand::COMMAND_NAME => DebugContainerCommand::class,
DebugEventsCommand::COMMAND_NAME => DebugEventsCommand::class,
'debug:reset' => DebugResetCommand::class,
Copy link
Member

Choose a reason for hiding this comment

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

Let's leave it as it is

Copy link
Member

Choose a reason for hiding this comment

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

What is better, strings or constant? And why?
We should use one way in all packages.

Copy link
Member Author

Choose a reason for hiding this comment

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

@xepozz command name is useless with attributes and without attributes Symfony console raises deprecation warning.

Copy link
Member

Choose a reason for hiding this comment

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

I like constants because they already exist in console command classes and it's easy to reference to the names rather than writing the name again and keep them consistent

Co-authored-by: Sergei Predvoditelev <[email protected]>
@samdark samdark requested review from xepozz and vjik June 21, 2024 12:47
@samdark samdark merged commit cd4fe68 into master Jun 22, 2024
16 of 17 checks passed
@samdark samdark deleted the cleanup branch June 22, 2024 12:55
Comment on lines -83 to -85
"branch-alias": {
"dev-master": "3.0.x-dev"
},

Choose a reason for hiding this comment

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

this means somebody installing ^3.0@dev not longer composer can resolve itself. I my personal recommendation would be rename master to 3.0 or 3.x that avoids branch aliases and composer directly know what version a branch suppose to be without you need to handle or update branch aliases.

Copy link
Member

Choose a reason for hiding this comment

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

It was about the first time package splitting. Yii2 -> Yii3
Now just use dev-master if you want to get master upstream.
But I suggest to use tags. Now the package is unstable and there's one way to install it is to use dev-master branch.

Copy link

@alexander-schranz alexander-schranz Jul 2, 2024

Choose a reason for hiding this comment

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

Aware of that, but still a ^3.0@dev would atleast make sure semver is followed. Renaming master -> 3.x or 3.0 would tell composer automatically what future version is and allow projects do ^3.0@dev. Also if you tag in future the 3.0.0 will a branch named 3.0 or 3.x will composer help to install that branch when somebody allow stability dev. With a branch named master without a branch alias composer can not detect the version. Its also one of the cases why example Symfony and we @sulu use minor version names as branches for all our packages as that helps composer with version detection for dev branches.

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.

5 participants