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

Allow Config::merge to accept a basic array. #13830

Merged
merged 7 commits into from
Feb 16, 2019
Merged

Allow Config::merge to accept a basic array. #13830

merged 7 commits into from
Feb 16, 2019

Conversation

dschissler
Copy link
Contributor

I created a new clean PR with the alternate option that I presented in the last PR. This will sit here for a few days until I have time to do the change log and to see about augmenting the tests.

ps. I wrote a metric shit load of zephir code today.

@codecov
Copy link

codecov bot commented Feb 15, 2019

Codecov Report

Merging #13830 into 4.0.x will increase coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##            4.0.x   #13830      +/-   ##
==========================================
+ Coverage   66.24%   66.24%   +<.01%     
==========================================
  Files         450      450              
  Lines       89628    89644      +16     
==========================================
+ Hits        59375    59388      +13     
- Misses      30253    30256       +3
Impacted Files Coverage Δ
ext/phalcon/config.zep.c 94.41% <0%> (-0.36%) ⬇️
ext/phalcon/di.zep.c 73.69% <0%> (-0.14%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update af35d0c...aa30fa9. Read the comment docs.

Copy link
Member

@niden niden left a comment

Choose a reason for hiding this comment

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

@dschissler This is solid. Can you please write a test and update the changelog?

@dschissler

This comment was marked as abuse.

let config = configParam;
break;
default:
throw new \Exception("Invalid data type for merge.");
Copy link
Contributor

Choose a reason for hiding this comment

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

Phalcon\Config\Exception

Copy link
Member

Choose a reason for hiding this comment

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

Yes and this one! Sorry missed it

@dschissler

This comment was marked as abuse.

@dschissler dschissler closed this Feb 16, 2019
@dschissler dschissler reopened this Feb 16, 2019
@dschissler

This comment was marked as abuse.

@niden niden added the enhancement Enhancement to the framework label Feb 16, 2019
@niden niden merged commit 83352b9 into phalcon:4.0.x Feb 16, 2019
@niden
Copy link
Member

niden commented Feb 16, 2019

Thank you @dschissler

@dschissler

This comment was marked as abuse.

@niden
Copy link
Member

niden commented Feb 16, 2019

@dschissler As a general rule (self imposed) we use the squash and merge option when merging.

@dschissler

This comment was marked as abuse.

@niden
Copy link
Member

niden commented Feb 17, 2019

@dschissler Honestly I still haven't sat down to read how to squash stuff on my local repo, so I do it here on github. ;)

@niden niden added the documentation Documentation required label Apr 9, 2019
@niden niden added 4.0 and removed documentation Documentation required labels Oct 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement to the framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants