Closed michaelkohn closed 1 day ago
Original for tracking: https://github.com/medic/cht-core/issues/8181
@michaelkohn I've separated this one into two tickets just for internal project management, while keeping the big ticket in https://github.com/medic/cht-core/issues/8181 Two people working simultaneously will step on each other because the files to refactor are the same (reports and contact pages)
Gotcha, thanks.
One other thing to consider is that, while we did agree that we can remove those feature flags earlier / in a separate release from the NAV updates themselves, my hope is that they are not released with a big time gap between them. If it's not much extra work, I'd like to keep the feature flags around as long as possible before we release the NAV updates. The logic is... if there is something that projects need / want in a release between when we remove the old feature flags and when we add the new NAV, I don't want the removal of the old feature flags to become a blocker for those projects (since the new UI will likely become one).
@michaelkohn is this still part of Q3 KRs?
Yes
@michaelkohn All tasks are completed. When we agree to release this work, we update this PR with the latest changes in CHT Core, do a final review, final test, and merge for releasing it in CHT.
Leaving this KR open for now
👍 perfect, thanks @latin-panda
Work delivered (PR)
CHT Core ticket: https://github.com/medic/cht-core/issues/8181
To achieve that we need to complete these 3 tasks: