Timeline for Hiding/disabling features for some users
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 17, 2018 at 16:02 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 103 characters in body
|
| May 16, 2018 at 5:48 | comment | added | Doc Brown |
@LorenPechtel: you should read my answer again, more carefully. I actually mentioned two things to reduce the number of conditional tests, one of them the DRY principle, one of them focussing on tests in UI. More important, mapping an unspecific flag like isFreeVersionto specific feature parameters removes most of the pain of those tests - they will actually start to make sense and don't produce a maintenance mess any more.
|
|
| May 16, 2018 at 3:17 | comment | added | Loren Pechtel | You have basically replaced IsFreeVersion with FeaturexEnabled, you haven't reduced the number of calls. While I haven't had exactly that case I've always handled similar stuff by upon menu creation disabling those options that the user shouldn't see. Mostly this is at form creation but I've sometimes had to do it when preparing a pop-up menu. | |
| May 15, 2018 at 11:57 | history | edited | Doc Brown | CC BY-SA 4.0 |
deleted 4 characters in body
|
| May 15, 2018 at 10:57 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 425 characters in body
|
| May 15, 2018 at 7:14 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 184 characters in body
|
| May 14, 2018 at 20:54 | history | answered | Doc Brown | CC BY-SA 4.0 |