Pietro/shifts family
1 open thread
1 open thread
It all the data, it's not clear we need to group shifts. It might be even worth it to change the granularity and a "shift" (title, description, etc) with an array of dates. Similar to a project, but presented differently...
Edited by pietro
Merge request reports
Activity
26 {{#each group in family.groups}} 27 {{#each shift in group.shifts }} 28 <tr class="shift {{family.class}} collapse" data-id="{{shift._id}}"> 29 <td> 30 {{#if $eq shift.priority "essential"}} 31 <div class="text-danger">{{fa "exclamation-circle"}}</div> 32 {{/if}} 33 </td> 34 <td>{{> shiftDateInline shift}}</td> 35 <!-- <td> 36 {{shift.title}} 37 {{#if ($eq shift.policy 'public')}}{{fa 'globe'}}{{/if}} 38 {{#if ($eq shift.policy 'private')}}{{fa 'user-secret'}}{{/if}} 39 {{#if ($eq shift.policy 'requireApproval')}}{{fa 'lock'}}{{/if}} 40 </td> --> 41 <td class="pull-rigth"> added 6 commits
-
4622354d...37958cff - 4 commits from branch
master
- 6aece6eb - Make skills and quirks required fields in the vol form
- ad1a445e - Group shifts accordingly to their title
-
4622354d...37958cff - 4 commits from branch
Please register or sign in to reply