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

Do not dump config file if config was changed #2035

Merged
merged 13 commits into from
Dec 25, 2019
Merged

Conversation

sergeyklay
Copy link
Member

Hello!

  • Type: bug fix
  • Link to issue: -

In raising this pull request, I confirm the following:

  • I have checked that another pull request for this purpose does not exist
  • I wrote some tests for this PR
  • I updated the CHANGELOG

Small description of change:

Usually we need dump configuration exactly once - at project initialization. There are no needs to dump it for every config change. Also, this patch removes Config::$changed variable that is no longer needed.

Thanks

@codecov
Copy link

codecov bot commented Dec 25, 2019

Codecov Report

Merging #2035 into development will decrease coverage by <.01%.
The diff coverage is 56%.

@@                Coverage Diff                @@
##             development    #2035      +/-   ##
=================================================
- Coverage          35.62%   35.62%   -0.01%     
- Complexity          8213     8216       +3     
=================================================
  Files                562      562              
  Lines              45316    45330      +14     
=================================================
+ Hits               16146    16149       +3     
- Misses             29170    29181      +11

@sergeyklay sergeyklay merged commit 10b19df into development Dec 25, 2019
@sergeyklay sergeyklay deleted the fix/config-dump branch December 25, 2019 22:19
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.

None yet

1 participant