Closed pinaf closed 9 years ago
@karato travis failure is unrelated to issue. see #299
@pinaf Thanks for your pull request, let me find someone who can review it
@krzyk review it
@pinaf I have one comment regarding the todo
@krzyk ok changed it. please take another look.
@karato we are waiting for #299
@karato we are waiting for #299
@krzyk yes, of course, we'll wait for #299
@pinaf qulice fails with:
[ERROR] /src/main/java/com/nerodesk/takes/doc/TkDirCreate.java[50-50]: Perhaps 'base' could be replaced by a local variable. (SingularField)
[ERROR] /src/main/java/com/nerodesk/takes/doc/TkDirCreate.java[50-50]: Avoid unused private fields such as 'base'. (UnusedPrivateField)
@pinaf we waited for #299, it is closed already
@yegor256 we might have to postpone this feature. directory implementation is going cause a few code challenges: directory deletion, moving files to another directory, and reorganizing files if the directory is deleted, etc. could be several tickets to scale this feature.
@yegor256 what do you think?
@karato indeed, let's postpone this
@karato indeed, let's postpone this
@yegor256 OK, I labeled it as "postponed" tag
@karato indeed, let's postpone this
@yegor256 right, I'll try to find someone else for this task
@longtimeago review it
@k0r @yegor256 not sure this was intentional or not, but ever since I have been added to the nerodesk team I have permission to merge the pull request...
@pinaf nerodesk
team has write
permission.
@k0r so it was intentional?
@pinaf #271
@k0r please fix it. the team must have "read-only" permissions
@yegor256 fixed.
@k0r you can also remove me and @karato from nerodesk-read team
@karato please, be careful with the labels.
@yegor256 shall we proceed with CR ?
@pinaf good question .. I'm also waiting for the answer
@yegor256 and why was it reassigned? I think it should have been unassigned completely until @k0r decides we should go with directories
@longtimeago I think we should proceed, review and merge. It's a pull request, we shouldn't hold it open for long time. (no matter what the status of the project is)
@k0r my bad, I thought it's an issue, not a pull request. It's not a good practice to keep pull requests in "on hold" status for longer. It will "expire" and we'll seriously damage the motivation of its author. It's always better to merge, no matter how "bad" is the code (well, it has to pass rultor and code review, of course).
@yegor256 postponing the feature isn't intended to demotivate the programmer, it involves other challenges we've previously discussed here.
@k0r yes, postponing a feature is perfectly fine, but it's a pull request, not a feature. there is already some code written.
@yegor256 thanks. proceed, if needed.
@yegor256 in such case can we reassign it to back to me, as I already reviewed it and, the only thing that is left is saying "merge" :-)
@krzyk I don't mind :)
@karato please assign @krzyk here
@yegor256 could you assign @krzyk please?
@karato assign @krzyk to this pls
@karato assign @krzyk to this pls
@yegor256 OK. @krzyk the ticket is yours, please proceed
@rultor merge pls
@rultor merge pls
@krzyk Thanks for your request. @yegor256 Please confirm this.
@rultor merge
@rultor merge
@yegor256 OK, I'll try to merge now. You can check the progress of the merge here
@rultor merge
@yegor256 Done! FYI, the full log is here (took me 10min)
@krzyk Thanks a lot, I just topped your account for 21 mins, transaction ID 58657984
, total time was 1 hour and 5 mins... extra minutes for review comments (c=6)... +21 added to your rating, at the moment it is: +4684
@rultor deploy now pls
For #221
TkDirCreate
+ unit testTkDir
now takes instance ofBase
in constructorDir
andDirs
RqDir
class for bridge between request andDir