-
Notifications
You must be signed in to change notification settings - Fork 1
TT-317 remove feature manager service #739
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
Conversation
…ort.guard and their dependants
…17-Remove-FeatureManagerService
Codecov Report
@@ Coverage Diff @@
## master #739 +/- ##
==========================================
+ Coverage 95.24% 95.54% +0.30%
==========================================
Files 106 106
Lines 2206 2247 +41
Branches 169 169
==========================================
+ Hits 2101 2147 +46
+ Misses 61 57 -4
+ Partials 44 43 -1
Continue to review full report at Codecov.
|
* fix: TT-319 Fix calendar week and day view * refactor: TT-319 select first day of the month when select on calendar * refactor: TT-319 Change moment library with date Co-authored-by: Andrés Soto <edansrock>
… toggle ui-list-technologies (#736) * perf: TT-316 removal of ui-list-technologies toggle, technologies-report.guard and their dependants * code-smell: TT-316 remove comments and unnecessary variable assignments * code-smell: TT-316 removal of an additional unnecessary import
…com/ioet/time-tracker-ui into TT-317-Remove-FeatureManagerService
…com/ioet/time-tracker-ui into TT-317-Remove-FeatureManagerService
Kudos, SonarCloud Quality Gate passed!
|
Task
The main idea was to remove the FeatureManagerService service entirely, to avoid direct calls to Azure-toggles when reloading the Time-Tracker application in the browser. Instead, we shall use CookieService. Therefore, in principle, it was necessary to remove FeatureManagerService from everywhere it was used, and also the tests that included the service.
Observation and solution
It was not possible to remove FeatureManagerService entirely, because CookieService depended from it. However, by removing two methods from FeatureManagerService we are achieving our goal which is to avoid calling Azure-toggles every time we reload the webpage. Instead, with the current configuration, we call Azure-toggles just at login, and then, CookieService is used the rest of the session.