-
Notifications
You must be signed in to change notification settings - Fork 203
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
Constructors of FkHitRefresh shouldn't throw any exceptions. #744
Comments
@yegor256 please, pay attention to this issue |
@skapral thanks! Please, submit a pull request, if you can. |
@skapral this job was assigned to you 8 days ago. |
Oops! Job |
1 similar comment
Oops! Job |
@t-izbassar The impediment for #744 was registered successfully by @t-izbassar/z |
@skapral ping |
@elenavolokhova/z please review this job, as in §30 |
@yegor256 This ticket violates QA rule:
Desision to let @skapral to deliver a solution to his own ticket led to incorrect situation here:
Please, confirm that you'll try to avoid assigning problem reporter to his own issue in future. I assume the quality of this ticket is bad. Please, let me know, if I'm wrong. |
@elenavolokhova can you inform 0crat about quality? Personally, I agree with you. I need this task to be closed by 0crat so that I can handle next one - thus you need to inform 0crat about the decision. |
@t-izbassar Sure. |
@0crat Quality is bad here. |
@elenavolokhova Argument "is" doesn't match regex |
@0crat Quality bad |
@elenavolokhova Can't understand "bad", try one of these:
|
@0crat quality bad |
QA review completed: +15 points just awarded to @elenavolokhova/z, total is +15 |
@0crat status |
The issue was raised after this discussion - http://disq.us/p/1lgf1ax.
According to this post, constructors should not do any logic inside. For Takes framework, this rule is violated in several places. One of them is the class
org.takes.facets.fork.FkHitRefresh
, which handles with IO inside a constructor.PS: @yegor256 please consider me as a contributor to solve this issue.
The text was updated successfully, but these errors were encountered: