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

Fixed a bug with the yii serve command and a custom router #20006

Merged
merged 1 commit into from
Oct 14, 2023

Conversation

angrybrad
Copy link
Contributor

If you supply a custom router and the path has a space in it, things break.

Q A
Is bugfix? ✔️
New feature?
Breaks BC?
Fixed issues #20005

…r was supplied and it had a space in the path
@codecov
Copy link

codecov bot commented Oct 13, 2023

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (4fe40f9) 48.95% compared to head (9875ae6) 48.95%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #20006   +/-   ##
=======================================
  Coverage   48.95%   48.95%           
=======================================
  Files         445      445           
  Lines       42826    42826           
=======================================
  Hits        20964    20964           
  Misses      21862    21862           
Files Coverage Δ
framework/console/controllers/ServeController.php 11.32% <0.00%> (ø)

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

@angrybrad angrybrad changed the title Fixed a bug where the yii serve command with custom router Fixed a bug with the yii serve command and a custom router Oct 13, 2023
@bizley bizley added this to the 2.0.50 milestone Oct 14, 2023
@bizley bizley merged commit 5a4c048 into yiisoft:master Oct 14, 2023
48 of 49 checks passed
@bizley
Copy link
Member

bizley commented Oct 14, 2023

Thank you.

@terabytesoftw
Copy link
Member

This PR broke the use of yii serve with the error Fatal error: Uncaught ValueError: Path cannot be empty in [no active file]:0 Stack trace: #0 {main} thrown in [no active file] on line 0 when executed.

@bizley
Copy link
Member

bizley commented Oct 20, 2023

Oh 😕 This looked really ok for me. Could you fix it @terabytesoftw ?

@xicond
Copy link
Contributor

xicond commented Oct 21, 2023

can include in 2.0.50 ?

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

Successfully merging this pull request may close these issues.

4 participants