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

Be more precise when refuse to expire #29646

Merged
merged 1 commit into from
Nov 24, 2017
Merged

Be more precise when refuse to expire #29646

merged 1 commit into from
Nov 24, 2017

Conversation

VicDeo
Copy link
Member

@VicDeo VicDeo commented Nov 21, 2017

Change the wording to be more clear

Description

Change the wording to be more clear

Related Issue

#28509

Motivation and Context

Unclear output

How Has This Been Tested?

By reading the message

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@tomneedham
Copy link
Contributor

Text looks good, not tested the code as it is just a string change 👍

@codecov
Copy link

codecov bot commented Nov 22, 2017

Codecov Report

Merging #29646 into master will increase coverage by 0.06%.
The diff coverage is 100%.

Impacted file tree graph

@@             Coverage Diff              @@
##             master   #29646      +/-   ##
============================================
+ Coverage     62.09%   62.16%   +0.06%     
  Complexity    17515    17515              
============================================
  Files          1045     1045              
  Lines         57746    57738       -8     
============================================
+ Hits          35858    35890      +32     
+ Misses        21888    21848      -40
Impacted Files Coverage Δ Complexity Δ
apps/files_trashbin/lib/Command/ExpireTrash.php 35.55% <100%> (+35.55%) 12 <0> (ø) ⬇️
apps/files_versions/lib/Command/ExpireVersions.php 36.36% <100%> (+36.36%) 12 <0> (ø) ⬇️

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 dc38ca0...98986a5. Read the comment docs.

@DeepDiver1975
Copy link
Member

Please add tests. Use command Tester. See other command tests like app commands

@VicDeo
Copy link
Member Author

VicDeo commented Nov 22, 2017

@DeepDiver1975 test that "Auto expiration is configured - expiration will be handled automatically." is actually printed char by char?

@PVince81
Copy link
Contributor

@VicDeo I usually use assertContains with a few keywords. Maybe there was no actual test at all for that code path so adding one would be nice.

@DeepDiver1975
Copy link
Member

@VicDeo
Copy link
Member Author

VicDeo commented Nov 23, 2017

Covered



/**
* Class ExpireTrashTest
Copy link
Contributor

Choose a reason for hiding this comment

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

uh oh, class name mismatch

Copy link
Contributor

@PVince81 PVince81 left a comment

Choose a reason for hiding this comment

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

👍 fix the phpdoc and this is good to go

@VicDeo
Copy link
Member Author

VicDeo commented Nov 23, 2017

@PVince81 fixed, history squashed, waiting for CI

@VicDeo
Copy link
Member Author

VicDeo commented Nov 24, 2017

Stable10: #29671

@PVince81 what about stable9.1?

@PVince81
Copy link
Contributor

If not critical I'd say no need to backport for 9.1.

@felixboehm felixboehm removed this from the triage milestone Apr 10, 2018
@lock
Copy link

lock bot commented Jul 31, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants