gergely
/
calendar-social
1
0
Fork 2
Code Issues 24 Pull Requests 3 Releases Wiki Activity

[WIP] Calculate response visibility #91

Draft
gergely wants to merge 2 commits from response-visibility into master
pull from: response-visibility
merge into: gergely:master
Conversation 0 Commits 2 Files Changed 2
gergely commented 2018-07-17 07:36:18 +00:00
Owner

This is the implementation of my original response visibility calculation (see #90). Now I truly doubt this should be the way, but it will be good as a reference.

This is the implementation of my original response visibility calculation (see #90). Now I truly doubt this should be the way, but it will be good as a reference.
gergely changed title from WIP: Calculate response visibility to [WIP] Calculate response visibility 2018-07-17 07:42:07 +00:00
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something is not working   
duplicate

This issue or pull request already exists   
enhancement

New feature   
help wanted

Need some help   
invalid

Something is wrong   
question

More information is needed   
wontfix

This won't be fixed
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gergely/calendar-social#91
There is no content yet.
Delete Branch "response-visibility"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?