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

GH-158 - Report the number of engagement reports submitted within a given time frame #232

Merged
merged 11 commits into from
Nov 1, 2017

Conversation

evdhoudt
Copy link
Contributor

No description provided.

@evdhoudt evdhoudt changed the title GH-158 - Report future engagement by location GH-158 - Report the number of engagement reports submitted within a given time frame Oct 31, 2017
@gjvoosten
Copy link
Collaborator

One commit probably refers to the wrong issue (should be #158).

}

public boolean getIncludeEngagementDayOfWeek() {
return (includeEngagementDayOfWeek == null) ? false : includeEngagementDayOfWeek;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Better to use:
return Boolean.TRUE.equals(includeEngagementDayOfWeek);
(should actually be changed elsewhere in the file as well).

@@ -15,6 +15,8 @@
Integer authorId;
DateTime engagementDateStart;
DateTime engagementDateEnd;
Integer engagementDayOfWeek;
Boolean includeEngagementDayOfWeek;
Copy link
Collaborator

@gjvoosten gjvoosten Oct 31, 2017

Choose a reason for hiding this comment

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

I prefer to make new fields private (at some point [e.g. when we have decided on a Checkstyle profile] we should consider changing them all).

@@ -37,6 +37,7 @@
DateTime releasedAt;

DateTime engagementDate;
Integer engagementDayOfWeek;
Copy link
Collaborator

@gjvoosten gjvoosten Oct 31, 2017

Choose a reason for hiding this comment

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

I prefer to make new fields private (at some point [e.g. when we have decided on a Checkstyle profile] we should consider changing them all).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

}

if (value.end !== null) {
this.updateDate("endDate", moment(value.end))
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed input to value.end

@evdhoudt evdhoudt merged commit 6df2f49 into candidate Nov 1, 2017
@evdhoudt evdhoudt deleted the GH-158 branch November 1, 2017 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants