Note, the assumption is that none of these items will lead to breaking, API-level changes. If any do, then they need to added to a new card and marked with next milestone version: 3.0.0.
It is worth going through the tech-debt backlog to see if there is anything else worth prioritising.
Update Frameworks and Packages
[x] #1285
[x] #1305
[x] #1159
[x] #819
[x] Refactoring of Dependency Injection for client (introduce the keyed registration)
[ ] #1052
[ ] Update other outdated/deprecated packages
Build Warnings
Some of the existing warnings maybe resolved by updating packages.
[ ] Remove non-API level code that was marked obsolete in previous Atlas versions (API-level code should be removed under a 3.0.0 ticket)
Note, the assumption is that none of these items will lead to breaking, API-level changes. If any do, then they need to added to a new card and marked with next milestone version:
3.0.0
.It is worth going through the tech-debt backlog to see if there is anything else worth prioritising.
Update Frameworks and Packages
Build Warnings
Some of the existing warnings maybe resolved by updating packages.
3.0.0
ticket)