User:Stuart/Scratchpad II: Difference between revisions
Jump to navigation
Jump to search
Stories |
m Added link to story |
||
| Line 1: | Line 1: | ||
== Stories for {{ep|10|Permissions Overhaul}} == | == {{us|68}} - Stories for {{ep|10|Permissions Overhaul}} == | ||
* Split compound methods into separate methods | * Split compound methods into separate methods | ||
** The archetypal example is changing a password, but there are others | ** The archetypal example is changing a password, but there are others | ||
Revision as of 08:15, 7 September 2016
US-68 - Stories for EP-10: Permissions Overhaul
- Split compound methods into separate methods
- The archetypal example is changing a password, but there are others
- Tidy up existing methods
- There are some methods which are unused from the interface - either, they're only used from within
clsServeritself, or they're not used at all. These should be sorted out. - Equally, there are some which are just single line calls of another method - this is fine when it's just a class, but when we need to maintain > 1 file for each method, and apply behaviour to each individual method, it becomes somewhat wasteful. eg.
HasSchedulerDataUpdatedandHasFontDataUpdatedare just single line calls toHasDataUpdatedwith a first argument of"Schedule"or"Font", respectively.- Actually, that's as far as my examples went
- There are some methods which are unused from the interface - either, they're only used from within
- Enumerate the new permissions required
- Tie them into the current permissions, ie. for each current permission, detail the set of new permissions that a user with that permission would end up with
- Assign the new permissions to the IServer methods